CVE-2025-11148
published 2025-09-30CVE-2025-11148: 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…
PriorityP263critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
1.39%
68.9th percentile
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.
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
check-branches is vulnerable to command Injection
ghsa·2025-09-30
CVE-2025-11148 [CRITICAL] CWE-77 check-branches is vulnerable to command Injection
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.
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.
OSV
check-branches is vulnerable to command Injection
osv·2025-09-30
CVE-2025-11148 [CRITICAL] check-branches is vulnerable to command Injection
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.
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-09-30
Published