GitHub Advisoryadvisory · npm

GHSA-9c4g-fp4r-prrv check-branches is vulnerable to command Injection

CRITICAL Published 2025-09-30 Modified 2025-10-03 Official page ↗
Aliases
CVE-2025-11148
Ecosystem
npm
Packages
check-branches
Severity
Critical
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-77, CWE-78
Reviewed
2025-09-30

Affected packages

• npm check-branches: <= 0.0.19 (no fix yet)

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.

Related

Alias · CVE (1)

  • CVE-2025-11148 All versions of the package check-branches are vulnerable to Command Injection check-branches is a command-line tool that is interacted… vulnerability

Weakness · CWE (2)

  • CWE-77 Improper Neutralization of Special Elements used in a Command weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command weakness

References