CVE-2026-6951
Simple-git remote code execution
- Published25 Apr 2026
Description
Versions of the package simple-git before 3.36.0 are vulnerable to Remote Code Execution (RCE) due to an incomplete fix for [CVE-2022-25912](https://security.snyk.io/vuln/SNYK-JS-SIMPLEGIT-3112221) that blocks the -c option but not the equivalent --config form. If untrusted input can reach the options argument passed to simple-git, an attacker may still achieve remote code execution by enabling protocol.ext.allow=always and using an ext:: clone source.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-6951
- https://bugzilla.redhat.com/show_bug.cgi?id=2461750
- https://gist.github.com/KKC73/02d1d97f3410756095b501fda0ac8ca6
- https://github.com/steveukx/git-js/commit/89a2294febed5dfe737c4c735d936bb6018746a8
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-6951.json
- https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-16300211
- https://security.snyk.io/vuln/SNYK-JS-SIMPLEGIT-15456078
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-6951 being actively exploited?
CVE-2026-6951 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.01%.
How severe is CVE-2026-6951?
CVE-2026-6951 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.01% probability of exploitation.
Which products are affected by CVE-2026-6951?
Affected products include Simple-git.
How do I fix CVE-2026-6951?
Upgrade affected software to a fixed version, for example Simple-git 3.36.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-6951 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.