ghsa-9c4g-fp4r-prrv
Vulnerability from github
Published
2025-09-30 12:30
Modified
2025-09-30 21:08
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
check-branches is vulnerable to command Injection
Details

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.

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "check-branches"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "0.0.19"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-11148"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-77",
      "CWE-78"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-09-30T21:08:04Z",
    "nvd_published_at": "2025-09-30T11:37:38Z",
    "severity": "CRITICAL"
  },
  "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.",
  "id": "GHSA-9c4g-fp4r-prrv",
  "modified": "2025-09-30T21:08:04Z",
  "published": "2025-09-30T12:30:51Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "check-branches is vulnerable to command Injection"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.