# CVE-2025-11148: check-branches is vulnerable to command Injection

> Attackers can execute arbitrary commands by crafting malicious git branch names, affecting users of the check-branches npm package.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** No
- **Published:** 30 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-9c4g-fp4r-prrv

## What is CVE-2025-11148?

CVE-2025-11148 is a critical command injection vulnerability in check-branches, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of the package check-branches are vulnerable to Command Injection check-branches is a command-line tool that is interacted with locally, or via CI, to confirm no conflicts exist in git branches.

However, the library follows these conventions which can be abused:
1. It trusts branch names as they are (plain text)
2. It spawns git commands by concatenating user input

Since a branch name is potentially a user input - as users can create branches remotely via pull requests, or simply due to privileged access to a repository - it can effectively be abused to run any command.

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

## Which versions are affected by CVE-2025-11148?

2 open source packages ship an affected version, including check-branches.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `check-branches` | npm | All versions to 0.0.19 | None |
| `check-branches` | npm | All versions to 0.0.19 | None |

## How do I fix CVE-2025-11148?

No fix has been published for CVE-2025-11148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11148 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11148 and fix it if it is affected.

What it is: CVE-2025-11148 is a critical command injection vulnerability in check-branches, published on 30 Sep 2025. 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-2025-11148 exists.

Affected packages and fixed versions:
- check-branches (npm): affected all versions up to 0.0.19; no fix listed
- check-branches (npm): affected all versions up to 0.0.19; no fix listed

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-2025-11148/ (Markdown: https://insights.sbomify.com/CVE-2025-11148/index.md)
```

## Sources

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

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