Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Arbitrary command execution yields full C:H/I:H/A:H and no auth to the library (PR:N), but exploitation requires the consumer to expose attacker-influenced push args plus a local/file remote, a condition beyond attacker control, so AC:H rather than AC:L.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
9DescriptionNVD
simple-git, an interface for running git commands in any node.js application, enables applications to execute Git operations from JavaScript. Prior to 4.0.0, the default blockUnsafeOperationsPlugin compares parsed option names with literal dangerous option spellings while Git accepts unambiguous long-option abbreviations. Attacker-influenced push arguments such as abbreviated --receive-pack or --exec forms can therefore bypass detectVulnerableFlags, reach git push against a local or file remote or an attacker-influenced receive-pack target, and cause Git to invoke an attacker-selected command in consumers that expose those arguments. The clone-side abbreviation handling does not protect the push path. This issue is fixed in 4.0.0.
AnalysisAI
Command injection in simple-git, the Node.js library for running git commands and published on npm, affects all releases before 4.0.0 and allows unauthenticated remote attackers to execute arbitrary commands whenever a consuming application forwards attacker-influenced values into a git push argument list. The library's default blockUnsafeOperationsPlugin matches dangerous options by literal spelling only, so unambiguous Git long-option abbreviations such as --receive-p, --receive-pa and --exe bypass detection, are expanded by Git itself, and reach --receive-pack on a local or file remote where the injected command runs. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
No credit card · 7-day full trial
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Three conditions must hold simultaneously: (1) the consuming application must forward attacker-influenced values into a simple-git push argument list; (2) the push must target a local or file remote, or an attacker-influenced receive-pack target, so that Git itself invokes the injected command; and (3) the application must rely on the default blockUnsafeOperationsPlugin without having opted into unsafe:{allowUnsafePack:true}. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals conflict sharply here. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade to simple-git 4.0.0 (https://github.com/steveukx/git-js/releases/tag/simple-git@4.0.0), which is the vendor-released fix delivered via PR https://github.com/steveukx/git-js/pull/1193 and commit https://github.com/steveukx/git-js/commit/98864c678444d9336357c844efa4fd5a7984c0d7; the v4 branch rejects abbreviated long options outright (throwing GitConfigurationError), filters ambient environment variables into the git child process, and requires a double opt-in (both allowEnvoronment and unsafe.allowUnsafeTemplateDir) for previously implicit unsafe behaviours. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all applications and services that depend on simple-git by scanning package manifests and running 'npm ls simple-git'; flag any version below 4.0.0 and identify code paths that pass untrusted input to git push. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same weakness CWE-77 – Command Injection
View allSame technique Command Injection
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-89333
GHSA-858h-whjf-mvg5