Quick answers
- Is CVE-2026-102827 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102827 being exploited in the wild.
- How severe is CVE-2026-102827?
- 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-102827?
- 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-102827 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102827?
- 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 performs literal string matching on Git options but does not account for Git's support of unambiguous long-option abbreviations. Attackers can bypass detection by using shortened forms of dangerous options like --receive-pack or --exec, reaching git push with a local/file remote or attacker-controlled receive-pack target, leading to arbitrary command execution. The vulnerability requires attacker influence over push arguments; it is fixed in version 4.0.0 through strict abbreviation blocking.
Affected products
- steveukx simple-git before 4.0.0
Identifiers
- CVE-2026-102827
- GHSA-858h-whjf-mvg5
Timeline
- 2026-09-29: disclosed: CVE-2026-102827 published
- 2026-09-23: patched: Fixed in version 4.0.0