Vulnerabilities in pkg:npm/check-branches

PACKAGE
Advisory Identifier: GHSA-9c4g-fp4r-prrv
Share
Advisory Summary

CVE-2025-11148 is a CRITICAL (CVSS 9.8) check-branches is vulnerable to command vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Check branches libraries in the npm ecosystem. The issue involves check-branches is vulnerable to command injection. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/check-branches

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/check-branches. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-9c4g-fp4r-prrv CVE-2025-11148 CRITICAL check-branches is vulnerable to command Injection

CVE-2025-11148 at a Glance

CVE Identifier CVE-2025-11148
GHSA Identifier GHSA-9c4g-fp4r-prrv
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Check branches
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-11148

To remediate this vulnerability, upgrade all affected Check branches dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

check-branches fixed: Latest secure release 
npm install check-branches@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls check-branches

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-11148, inspect your project dependencies using npm:

npm ls check-branches

Analyze the terminal output to locate any version of Check branches in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls check-branches command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Check branches, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2025-11148 Affected Check branches Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
check-branches
npm/check-branches
npm
≤ 0.0.19

References

NVD — CVE-2025-11148 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-11148
Check branches Source Repository REPOSITORY
https://gist.github.com/lirantal/054b4ad039a86c418f2c84e3e884d6ec
Check branches Source Repository REPOSITORY
https://github.com/puntorigen/check-branches
Check branches Security Information SECURITY
https://security.snyk.io/vuln/SNYK-JS-CHECKBRANCHES-2766494

Frequently Asked Questions

What is CVE-2025-11148?
CVE-2025-11148 is a security vulnerability in Check branches involving check-branches is vulnerable to command Injection under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Check branches versions are affected?
Affected versions include releases prior to current release patches across affected packages: check-branches.
What version fixes CVE-2025-11148?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is check-branches affected?
Yes, check-branches is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2025-11148?
CVE-2025-11148 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2025-11148?
CVE-2025-11148 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check npm dependencies for CVE-2025-11148?
Run the dependency tree command: 'npm ls check-branches'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9c4g-fp4r-prrv",
  "modified" : "2025-10-03T18:22:21Z",
  "published" : "2025-09-30T12:30:51Z",
  "aliases" : [ "CVE-2025-11148" ],
  "summary" : "check-branches is vulnerable to command Injection",
  "details" : "All versions of the package check-branches are vulnerable to Command Injection.\n\ncheck-branches is a command-line tool that is interacted with locally, or via CI, to confirm no conflicts exist in git branches.\n\nHowever, the library follows these conventions which can be abused:\n1. It trusts branch names as they are (plain text)\n2. It spawns git commands by concatenating user input\n\nSince 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "check-branches"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.0.19"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-11148"
  }, {
    "type" : "WEB",
    "url" : "https://gist.github.com/lirantal/054b4ad039a86c418f2c84e3e884d6ec"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/puntorigen/check-branches"
  }, {
    "type" : "WEB",
    "url" : "https://security.snyk.io/vuln/SNYK-JS-CHECKBRANCHES-2766494"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-77", "CWE-78" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-30T21:08:04Z",
    "nvd_published_at" : "2025-09-30T11:37:38Z"
  }
}