---
title: "CVE-2025-11148: check-branches is vulnerable to command Injection"
url: https://erroneo.us/security/cve/CVE-2025-11148/
description: "CVE-2025-11148 (check-branches (npm)): All versions of the package check-branches are vulnerable to Command Injection check-branches is a command-line tool…"
type: vulnerability-record
section: "Security Digest"
date_published: 2025-09-30
date_modified: 2025-10-03
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2025-11148"
kev: false
cvss: 9.3
epss: 0.01354
license: All rights reserved. Quote with attribution and a link.
---

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

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 1.4% , percentile 71: FIRST’s model estimates a 1.4% chance of exploitation activity in the next 30 days, higher than 71% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes check-branches (npm) <= 0.0.19, no fixed version listed . Check your lockfile, including transitive dependencies.

## What it is

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.

## Affected packages

- npm `check-branches` <= 0.0.19 → fixed: none listed

## Affected products (CVE record)

- n/a check-branches: < *

## Severity

- snyk CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
- GitHub CVSS 4.0: 9.3 `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 1.35% probability of exploitation activity in the next 30 days; percentile 71.

## Sources

- [GitHub Advisory GHSA-9c4g-fp4r-prrv](https://github.com/advisories/GHSA-9c4g-fp4r-prrv)
- [CVE.org record CVE-2025-11148](https://www.cve.org/CVERecord?id=CVE-2025-11148)
- [NVD entry CVE-2025-11148](https://nvd.nist.gov/vuln/detail/CVE-2025-11148)
- [security.snyk.io](https://security.snyk.io/vuln/SNYK-JS-CHECKBRANCHES-2766494)
- [gist.github.com](https://gist.github.com/lirantal/054b4ad039a86c418f2c84e3e884d6ec)

---
Source page: https://erroneo.us/security/cve/CVE-2025-11148/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt