CVE-2025-11148

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.

Severity
CRITICAL
CVSS v3
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · source cna
Exploit chance (EPSS)
1.403%
chance of exploitation in the next 30 days
higher than 73% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableyes
Technical impacttotal
Scored2025-09-30

Timeline

  1. 2025-09-30Published by the CNA05:00 UTC
  2. 2025-09-30GitHub advisory published (GHSA-9c4g-fp4r-prrv)same day
  3. 2025-09-30CISA SSVC decision recordedsame day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-9c4g-fp4r-prrv, affected packages:

PackageVulnerable versionsFixed in
npm check-branchesthrough 0.0.19

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources