CVE-2025-11148: check-branches · Command Injection
Affects check-branchesSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| check-branches | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should immediately audit their use of the 'check-branches' tool in local and CI environments. Specific recommendations include: 1) Avoid using 'check-branches' until a patched version is released; 2) If usage is unavoidable, implement strict branch naming policies that disallow special characters or shell metacharacters to prevent injection payloads; 3) Sanitize and validate branch names rigorously before processing; 4) Run CI jobs with the least privilege principle, restricting permissions of the user executing 'check-branches' to minimize potential damage; 5) Employ containerization or sandboxing for CI jobs to isolate potential command execution; 6) Monitor CI logs and system activity for suspicious command executions or anomalies; 7) Consider alternative tools or custom scripts that safely handle branch names; 8) Educate developers and repository maintainers about the risks of accepting untrusted branch names; 9) Implement network segmentation and access controls to limit exposure of build infrastructure; 10) Stay updated on vendor advisories and apply patches promptly once available.
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.