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.
Published: 2025-09-30
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD EUVD-2025-31701 check-branches is vulnerable to command Injection
Github GHSA Github GHSA GHSA-9c4g-fp4r-prrv check-branches is vulnerable to command Injection
History

Thu, 02 Oct 2025 09:00:00 +0000

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

Tue, 30 Sep 2025 19:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 30 Sep 2025 05:15:00 +0000

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

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Check-branches Project Check-branches
cve-icon MITRE

Status: PUBLISHED

Assigner: snyk

Published:

Updated: 2025-09-30T19:06:21.373Z

Reserved: 2025-09-29T09:12:03.488Z

Link: CVE-2025-11148

cve-icon Vulnrichment

Updated: 2025-09-30T19:06:12.881Z

cve-icon NVD

Status : Deferred

Published: 2025-09-30T11:37:38.883

Modified: 2026-04-15T00:35:42.020

Link: CVE-2025-11148

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2025-10-02T08:46:24Z

Weaknesses