Vulnerability · Published Sep 30, 2025 · Assigned by snyk

CVE-2025-11148

Critical 9.8

In plain English

A critical-severity OS command injection in check-branches. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 1.4% (higher than 72% of all known vulnerabilities).

Severity (CVSS 3.1)9.8Critical
Exploit odds (30 days)1.4%top 28.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmcheck-branchesno fix listedGHSA-9c4g-fp4r-prrv

Affected products (as reported)

VendorProductVersions
n/a check-branches 0 – before *

Weakness: CWE-78 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References