Quick answers
- Is CVE-2026-6951 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6951 being exploited in the wild.
- How severe is CVE-2026-6951?
- Critical severity, with a CVSS score of 9.8, published 25 April 2026.
- Which products and versions are affected?
- simple-git (npm) SEMVER:introduced=0,fixed=3.36.0.
- Is there a fix for CVE-2026-6951?
- Yes. simple-git (npm): upgrade to 3.36.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6951 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-6951?
- Check whether you run simple-git (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- simple-git (npm): upgrade to 3.36.0 or later
npm install simple-git@3.36.0
Technical details
The vulnerability exists in simple-git versions prior to 3.36.0. While a previous fix blocked the '-c' Git option to prevent configuration injection, it failed to block the equivalent '--config' flag. An attacker who can control the options argument passed to functions such as 'clone' can inject '--config protocol.ext.allow=always'. By combining this with an 'ext::' protocol source, the attacker can execute arbitrary shell commands. This is classified as Improper Control of Generation of Code (CWE-94). The issue is resolved in version 3.36.0.
Affected products
- steveukx simple-git >=3.15.0, <3.36.0
Identifiers
- CVE-2026-6951
- GHSA-hffm-xvc3-vprc
Timeline
- 2026-03-07: disclosed: Vulnerability disclosed and introduced in tracking.
- 2026-04-24: advisory: Snyk published the advisory.
- 2026-04-25: patched: Fix released in version 3.36.0.