dbcve.org
Simple GitApplication · Simple Git Project

CVE-2026-28292

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 3.32.2 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
`simple-git`, an interface for running git commands in any node.js application, has an issue in versions 3.15.0 through 3.32.2 that allows an attacker to bypass two prior CVE fixes (CVE-2022-25860 and CVE-2022-25912) and achieve full remote code execution on the host machine. Version 3.23.0 contains an updated fix for the vulnerability.

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 · moderate confidence

simple-git versions 3.15.0 through 3.32.2 contain a command injection vulnerability that bypasses prior fixes for CVE-2022-25860 and CVE-2022-25912, allowing unauthenticated attackers to execute arbitrary commands on the host system with the privileges of the Node.js process.

MitigationUpgrade simple-git to version 3.23.0 or later to apply the updated fix, then conduct regression testing to ensure existing git operations function correctly.

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.32.2

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. Identify installed simple-git version
    Run 'npm list simple-git' or 'yarn list simple-git' to see the installed version. Alternatively, check package.json for the simple-git dependency version.
    Affected if The installed version is 3.15.0 through 3.32.2 (any version >= 3.15.0 and < 3.32.2)
  2. Check if the application passes user input to git commands
    Review the source code that uses simple-git to see if any git method (such as push, pull, clone, or raw) receives parameters that could be influenced by external users or untrusted input.
    Affected if User-supplied or untrusted data flows into simple-git method arguments without sanitization
  3. Verify git configuration settings
    Inspect any git configuration that the application sets or modifies, particularly custom git config options or environment variables like GIT_SSH_COMMAND, GIT_CONFIG_GLOBAL, or GIT_SSHWrapper.
    Affected if The application configures git options that accept command strings or allows users to influence git configuration values

You are affected if simple-git version 3.15.0 through 3.32.2 is installed AND your application passes external input to simple-git methods or allows user influence over git configuration.

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.32.2 or later
Fixed in 3.32.2
Vendor patch github.com →
Interim mitigation

Upgrade simple-git to version 3.23.0 or later to apply the updated fix, then conduct regression testing to ensure existing git operations function correctly.

Recommended fix High confidence

simple-git version 3.32.2 or later

  1. 1. Check the current version of simple-git in your project by running `npm list simple-git` or reviewing package.json
  2. 2. Upgrade to version 3.32.2 or later by running `npm install simple-git@^3.32.2` or `npm install simple-git@latest`
  3. 3. Verify the upgrade was successful by running `npm list simple-git`
  4. 4. Run your application's test suite to ensure the upgrade does not break existing functionality
  5. 5. Redeploy your application to apply the changes
Caveat Review the changelog between your current version and 3.32.2 for any breaking changes, though minor version patches typically maintain backward compatibility

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

Fix this in Simple Git Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28292 — 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-28292 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