# CVE-2026-106058: GitAhead through 2.7.1 OS Command Injection via Git Filter Filenames

> GitAhead allows OS command injection via malicious repository filenames, enabling attackers to execute arbitrary code on the victim's machine.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-q252-mvpj-37m5

## What is CVE-2026-106058?

CVE-2026-106058 is a high-severity command injection vulnerability in gitahead, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-106058?


## How do I fix CVE-2026-106058?

No fix has been published for CVE-2026-106058 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106058 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106058 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106058 and fix it if it is affected.

What it is: CVE-2026-106058 is a high-severity command injection vulnerability in gitahead, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106058 exists.

Affected product: gitahead. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106058/ (Markdown: https://insights.sbomify.com/CVE-2026-106058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106058
- OSV: https://osv.dev/vulnerability/CVE-2026-106058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106058/
Summaries are generated and may contain mistakes; the official description above is the record.