Cyber Resilience

CVE-2026-28292

RCE in Simple-Git Project Simple-Git 3.15.0 – 3.32.2

Published
10 March 2026
Modified
15 July 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.013 68th percentile
Risk Priority 74 floored blend · peak EPSS

Summary

CVE-2026-28292 is a critical-severity OS Command Injection (CWE-78) vulnerability in Simple-Git Project Simple-Git. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 32% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-28292 is a critical vulnerability (CVSS 9.8, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) affecting the `simple-git` npm package, an interface for executing Git commands in Node.js applications. Versions 3.15.0 through 3.32.2 contain a flaw classified under CWE-78 (OS Command Injection) and CWE-178 (Improper Encoding or Escaping of Outputs), which enables attackers to bypass mitigations from prior vulnerabilities CVE-2022-25860 and CVE-2022-25912, resulting in full remote code execution on the host machine. The issue was published on 2026-03-10.

A remote attacker requires no privileges or user interaction and can exploit this over the network with low complexity. By crafting malicious input processed by `simple-git`, such as through Git repository URLs or commands, the attacker achieves arbitrary code execution on the host system, potentially leading to complete compromise including high confidentiality, integrity, and availability impacts.

The GitHub security advisory (GHSA-r275-fr43-pm7q) and related commit (f7042088aa2dac59e3c49a84d7a2f4b26048a257) detail the fix, with version 3.23.0 providing an updated patch. Security practitioners should upgrade to version 3.23.0 or later and review the CodeAnt.ai research for additional technical details on the bypass mechanism.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

`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…

more

host machine. Version 3.23.0 contains an updated fix for the vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1036 Masquerading Stealth
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-28291Same product: Simple-Git Project Simple-Git
CVE-2026-6951Same product: Simple-Git Project Simple-Git
CVE-2022-20708Shared CWE-78
CVE-2023-4249Shared CWE-78
CVE-2023-20007Shared CWE-78
CVE-2023-20076Shared CWE-78
CVE-2021-1473Shared CWE-78
CVE-2023-3261Shared CWE-78
CVE-2023-24958Shared CWE-78
CVE-2023-37032Shared CWE-78

Affected Assets

simple-git project
simple-git
3.15.0 — 3.32.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5
  • V1.2.8
  • V15.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect command sanitization during development.

Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.

Applying access control decisions to each request depends on accurate property determination that accounts for case differences.

Correct enforcement of authorizations for resource access structurally requires consistent case-sensitive handling of identifiers to avoid incorrect decisions.

Least privilege reduces the permissions available to any process that could be subverted by injected commands.

Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.

PR.PS-02 partial match
prevents

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.

prevents

Secure SDLC practices should include case-sensitivity requirements in design and coding standards.

prevents

Application security requirements must specify case handling for identifiers and paths.

prevents

Architecture principles should enforce canonical, case-aware resource naming.

prevents

Secure coding guidelines must mandate explicit case handling to prevent inconsistent lookups.

degrades

Access-control rules that ignore case can allow unintended resource access.

References