Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | check-branches | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Check-branches Project | Check-branches | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-31701 | check-branches is vulnerable to command Injection |
Github GHSA |
GHSA-9c4g-fp4r-prrv | check-branches is vulnerable to command Injection |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.4% (1.403% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Check-branches Project
Check-branches Project check-branches |
|
| Vendors & Products |
Check-branches Project
Check-branches Project check-branches |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Weaknesses | CWE-78 | |
| References |
| |
| Metrics |
cvssV3_1
|
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')