CVE-2026-28292
Remote Code Execution in simple-git via Patch Bypass
Publication date: 2026-03-10
Last updated on: 2026-04-14
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| simple-git_project | simple-git | From 3.15.0 (inc) to 3.32.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-178 | The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. |
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the simple-git library, which is used to run git commands within node.js applications. Versions 3.15.0 through 3.32.2 have a security flaw that allows an attacker to bypass two previous fixes (CVE-2022-25860 and CVE-2022-25912). This bypass enables the attacker to execute arbitrary code remotely on the host machine where the vulnerable simple-git version is running.
How can this vulnerability impact me? :
This vulnerability can have a severe impact as it allows an attacker to achieve full remote code execution on the affected host machine. This means the attacker can run any code they choose with the same privileges as the application using simple-git, potentially leading to data theft, system compromise, or further attacks within the network.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade the simple-git package to version 3.23.0 or later, as this version contains an updated fix that addresses the issue.