check-branches is vulnerable to command Injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-11148: 1.35% estimated exploitation activity in the next 30 days; percentile 71.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 by the source

30 Sep 2025, 12:30 UTC

Last modified by the source

3 Oct 2025, 18:22 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9c4g-fp4r-prrv

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9c4g-fp4r-prrv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-11148

Advisory: check-branches is vulnerable to command Injection
IDs: CVE-2025-11148, GHSA-9c4g-fp4r-prrv
Record: https://patchnext.com/advisories/cve-2025-11148 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm check-branches: affected <= 0.0.19

## Suggested inspection (read-only)
- `npm ls check-branches --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on check-branches.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9c4g-fp4r-prrv (OSV record GHSA-9c4g-fp4r-prrv lists affected ranges: npm check-branches >=0 <=0.0.19)
- Verified: https://github.com/advisories/GHSA-9c4g-fp4r-prrv (GitHub-reviewed advisory GHSA-9c4g-fp4r-prrv lists affected ranges: npm check-branches >=0 <=0.0.19)

Commands are suggestions: review each one before running it.