Quick answers
- Is CVE-2026-102826 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102826 being exploited in the wild.
- How severe is CVE-2026-102826?
- High severity, with a CVSS score of 8.1, published 29 September 2026.
- Which products and versions are affected?
- simple-git (npm) <= 3.36.0, SEMVER:introduced=0,fixed=4.0.0; Steveukx Simple-Git before 4.0.0.
- Is there a fix for CVE-2026-102826?
- Yes. simple-git (npm): upgrade to 4.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102826 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102826?
- Check whether you run simple-git (npm) or Steveukx Simple-Git 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 4.0.0 or later
npm install simple-git@4.0.0
Technical details
The blockUnsafeOperationsPlugin fails to completely reject include.path and includeIf.<condition>.path configuration options supplied through customArgs to git.clone(), allowing Git to load attacker-controlled configuration files. These configuration files can specify executable Git options like core.sshCommand that are invoked during clone operations with Node.js process privileges. Exploitation requires both attacker-influenced custom arguments and an attacker-controlled file readable by the process; the vulnerability is fixed in version 4.0.0.
Affected products
- steveukx simple-git before 4.0.0
Identifiers
- CVE-2026-102826
- GHSA-g4wm-2vf7-vfgr
Timeline
- 2026-09-29: disclosed
- 2026-09-23: patched: Fixed in version 4.0.0