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.
CVE-2026-106058
HIGHPre-NVD 7.57.5—Trending — 3 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-07. A secondary CVSS source baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 50EG Risk 50/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 7, 2026
Last Modified
October 7, 2026
Advisory Details (4)
Auto-updated Oct 7, 2026No fix on record yet.
generic
GitAhead through 2.7.1 OS Command Injection via Git Filter Filenames | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitahead-through-2.7.1-os-command-injection-via-git-filter-filenamesgeneric
gitahead/src/git/Filter.cpp at v2.7.1 · gitahead/gitahead · GitHub
https://github.com/gitahead/gitahead/blob/v2.7.1/src/git/Filter.cpp#L43-L70generic
GitHub - gitahead/gitahead: Understand your Git history! · GitHub
https://github.com/gitahead/gitaheadgeneric
[Security] OS command injection in git filter driver via crafted filename (%f substitution) — RCE · Issue #661 · gitahead/gitahead · GitHub
https://github.com/gitahead/gitahead/issues/661Vendor Advisories for CVE-2026-106058(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-07 21:26 UTCEG score recompute
- 2026-10-07 21:25 UTCGHSA enrichment
- 2026-10-07 21:01 UTCEG score recompute
- 2026-10-07 21:01 UTCGHSA enrichment
- 2026-10-07 16:13 UTCEG score recompute
- 2026-10-07 16:13 UTCGHSA enrichment
- 2026-10-07 12:21 UTCEG score recompute
- 2026-10-07 12:01 UTCEG score recompute
- 2026-10-07 12:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-106058?
CVE-2026-106058 is a high vulnerability published on October 7, 2026. 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…
When was CVE-2026-106058 disclosed?
CVE-2026-106058 was first published on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-106058?
CVE-2026-106058 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-106058?
No fix for CVE-2026-106058 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-106058 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-106058
Is Your Infrastructure Affected by CVE-2026-106058?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.