Arbitrary command execution via unescaped branch names
Published Sep 30, 2025 · Updated Sep 30, 2025
Command injection in check-branches 0.0.19 and earlier allows remote attackers to execute arbitrary commands through crafted Git branch names. The CLI trusts branch names as plain text and concatenates them into spawned Git commands without neutralizing shell metacharacters. Execution occurs when a developer or CI job runs the tool in a repository containing an attacker-controlled branch, with commands inheriting that process's privileges.
Summary
What happened
Command injection in check-branches 0.0.19 and earlier allows remote attackers to execute arbitrary commands through crafted Git branch names. The CLI trusts branch names as plain text and concatenates them into spawned Git commands without neutralizing shell metacharacters. Execution occurs when a developer or CI job runs the tool in a repository containing an attacker-controlled branch, with commands inheriting that process's privileges.
The record
- CVE
- CVE-2025-11148
- Published
- Sep 30, 2025
- Updated
- Sep 30, 2025
- Vendor
- Pablo Schaffner
- Product
- check-branches
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2025CVE publishedPublication date reported by the CVE source.
- Sep 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Snyk crafted-branch-name proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo