CVE-2026-106058

GitAhead through 2.7.1 OS Command Injection via Git Filter Filenames

Published Oct 7, 2026 CVSS 4.0 · 7.7 High EPSS 1.2% KEV · Not listed
Description
GitAhead through 2.7.1 contains an OS command injection vulnerability in src/git/Filter.cpp that allows malicious repositories to execute commands by substituting crafted filenames into clean/smudge filter commands. Attackers can ship files named with $(command) selected via .gitattributes so checkout or staging runs the command through bash -c as the victim.

Analysis

AI-generated

Technical impact

GitAhead through version 2.7.1 contains a CWE-78 OS command injection flaw in its clean and smudge filter logic located in src/git/Filter.cpp. The bug allows specially crafted filenames supplied by a malicious repository to be passed directly to the system shell via bash -c, giving an attacker the ability to execute arbitrary commands on the machine where GitAhead is running. This can lead to complete compromise of the operating system, data loss, or further lateral movement. The vulnerability is a classic case of improperly handling user‑supplied input that ends up being interpreted as shell code.

Affected Systems

The affected product is the GitAhead client, version 2.7.1. All installations of this release are vulnerable.

Risk and Exploitability

The CVSS score of 7.7 indicates a high severity and suggests that the vulnerability meets the criteria for remote code execution. The EPSS score of 1% indicates a very low but non‑zero probability of exploitation, and the issue has not been listed in the CISA KEV catalog, so no public exploitation data are currently known. Nevertheless, the attack would require an attacker to host or craft a repository with a .gitattributes file that references a filter and expose a filename containing a shell expansion such as $(id). When a victim runs git checkout, git add, or any other operation that triggers the filter, the victim’s shell will execute the injected command. Because the injected command runs with the same privileges as the GitAhead process, any user able to run GitAhead on a target machine could potentially steal data, install malware, or gain administrative rights.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to the latest GitAhead release that removes the vulnerability.
  • If an immediate upgrade is not possible, remove or disable smudge/clean filter support by deleting the relevant .gitattributes entries or setting git config filter.<name>.cleanup false.
  • Avoid cloning or pulling from untrusted or unknown repositories until a secure version is installed.

Generated by OpenCVE AI on October 8, 2026 at 18:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitahead
Gitahead gitahead
Vendors & Products Gitahead
Gitahead gitahead
Type Values Removed Values Added
Description GitAhead through 2.7.1 contains an OS command injection vulnerability in src/git/Filter.cpp that allows malicious repositories to execute commands by substituting crafted filenames into clean/smudge filter commands. Attackers can ship files named with $(command) selected via .gitattributes so checkout or staging runs the command through bash -c as the victim.
Title GitAhead through 2.7.1 OS Command Injection via Git Filter Filenames
Weaknesses CWE-78
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-78

    Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 7, 2026, 8:55 PM
Reserved
Oct 6, 2026, 2:14 PM
Status
Awaiting Analysis
Published
Oct 7, 2026, 12:17 PM
Modified
Oct 7, 2026, 9:17 PM