dbcve.org
Simple GitApplication · Simple Git Project

CVE-2026-6951

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-25
Fix available
A fix is available. Upgrade to 3.36.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

simple-git versions before 3.36.0 contain an incomplete fix for CVE-2022-25912. While the previous patch blocked the -c option, it failed to block the equivalent --config form, allowing attackers to pass protocol.ext.allow=always via --config and leverage the ext:: protocol in clone sources to achieve remote code execution when untrusted input reaches the options argument.

MitigationUpgrade simple-git to version 3.36.0 or later. Additionally, never pass untrusted user input directly to the options argument of simple-git methods.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simple GitApplication
Affected:>= 3.15.0, < 3.36.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed simple-git version
    Run `npm list simple-git` or `pip show simple-git` depending on your package manager, or inspect your package-lock.json / requirements.txt for the simple-git version
    Affected if Version is >= 3.15.0 and < 3.36.0
  2. Inspect code that calls simple-git with user input
    Search your codebase for calls to simple-git functions that accept configuration options, particularly looking for usage of the `--config` flag being passed user-controlled values
    Affected if User-supplied input is passed directly to simple-git configuration options without sanitization
  3. Check for protocol.ext.allow configuration
    Search your codebase or git configuration for `protocol.ext.allow=always` or similar settings being set via simple-git options
    Affected if protocol.ext.allow is set to always and controllable via user input passed to --config
  4. Check for ext:: protocol usage in clone operations
    Review any code that constructs clone URLs or passes git URLs to simple-git, looking for ext:: protocol handlers
    Affected if ext:: protocol URLs are being used or could be injected via user input to clone operations

Your environment is affected if simple-git version is between 3.15.0 and 3.36.0 AND your application passes unsanitized user input to simple-git configuration options (especially --config), which could enable protocol.ext.allow=always and ext:: protocol exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.36.0 or later
Fixed in 3.36.0
Vendor patch github.com →
Interim mitigation

Upgrade simple-git to version 3.36.0 or later. Additionally, never pass untrusted user input directly to the options argument of simple-git methods.

Recommended fix High confidence

simple-git 3.36.0

  1. Check package.json for simple-git dependency and all project references
  2. Run `npm install simple-git@^3.36.0` or `yarn add simple-git@^3.36.0` to update to the fixed version
  3. Verify the installed version is 3.36.0 or later with `npm list simple-git` or `yarn list simple-git`
  4. Rebuild and test the application to ensure git operations work correctly
  5. Scan the updated dependency with a security tool to confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Simple Git Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6951 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data