Security Digest · Vulnerability record

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

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.

CVSS 9.3 Critical EPSS 1.4% · p71

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • 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.

From the GitHub advisory

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 type: CWE-78, CWE-77.

Product: check-branches (npm) · Assigned by: snyk · Published: 2025-09-30

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
npmcheck-branches<= 0.0.19none listed
VendorProductAffected versions (per CVE record)
n/acheck-branches< *

Severity scores

Scored byCVSSScoreVector
snyk3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub4.09.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
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • 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.

Timeline

  • — CVE record last updated
  • — CVE record published by snyk
  • — GitHub-reviewed advisory GHSA-9c4g-fp4r-prrv published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-9c4g-fp4r-prrv github.com
  2. CVE.org record CVE-2025-11148 cve.org
  3. NVD entry CVE-2025-11148 nvd.nist.gov

Other references from the CVE record and advisory

  1. security.snyk.io security.snyk.io
  2. gist.github.com gist.github.com

Critical npm advisories · Today’s Security Digest