# CVE-2026-28291: simple-git has Command Execution via Option-Parsing Bypass

> Attackers can execute arbitrary commands by bypassing safety checks in the simple-git library through Git option manipulation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-jcxm-m3jx-f287, MINI-8h3p-w6vm-2wrr, ROOT-APP-NPM-CVE-2026-28291

## What is CVE-2026-28291?

CVE-2026-28291 is a high-severity command injection vulnerability in steveukx git-js, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

simple-git enables running native Git commands from JavaScript. Versions up to and including 3.31.1 allow execution of arbitrary commands through Git option manipulation, bypassing safety checks meant to block dangerous options like -u and --upload-pack. The flaw stems from an incomplete fix for CVE-2022-25860, as Git's flexible option parsing allows numerous character combinations (e.g., -vu, -4u, -nu) to circumvent the regular-expression-based blocklist in the unsafe operations plugin. Due to the virtually infinite number of valid option variants that Git accepts, a complete blocklist-based mitigation may be infeasible without fully emulating Git's option parsing behavior. This issue has been fixed in version 3.32.0.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-28291?

2 open source packages ship an affected version, including simple-git. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `simple-git` | npm | All versions | 3.32.0 |
| `simple-git` | npm | All versions | 3.32.0 |

Products: Simple-Git Project Simple-Git.

## How do I fix CVE-2026-28291?

Upgrade simple-git to 3.32.0 or later.

## Is CVE-2026-28291 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28291 exists.

## Other vulnerabilities in steveukx git-js

- [CVE-2026-28292](https://insights.sbomify.com/CVE-2026-28292/): simple-git has blockUnsafeOperationsPlugin bypass via case-insensitive protocol.allow config key that enables RCE (critical 9.8)
- [CVE-2026-102828](https://insights.sbomify.com/CVE-2026-102828/): simple-git unsafe-operation guard does not block trailer command configuration (critical 9.2)
- [CVE-2026-6951](https://insights.sbomify.com/CVE-2026-6951/): simple-git is vulnerable to Remote Code Execution (critical 9.2)
- [CVE-2026-102826](https://insights.sbomify.com/CVE-2026-102826/): simple-git allows command execution through unblocked Git configuration includes (high 8.1)
- [CVE-2026-102827](https://insights.sbomify.com/CVE-2026-102827/): simple-git: unsafe-operations plugin bypass via git long-option abbreviation (--receive-p/--exe) -> command execution (residual of CVE-2026-28291) (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28291 and fix it if it is affected.

What it is: CVE-2026-28291 is a high-severity command injection vulnerability in steveukx git-js, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28291 exists.

Affected packages and fixed versions:
- simple-git (npm): affected all versions; fixed in 3.32.0
- simple-git (npm): affected all versions; fixed in 3.32.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-28291/ (Markdown: https://insights.sbomify.com/CVE-2026-28291/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-28291
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28291
- OSV: https://osv.dev/vulnerability/CVE-2026-28291

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-28291/
Summaries are generated and may contain mistakes; the official description above is the record.