GHSA-9c4g-fp4r-prrv

Suggest an improvement
Source
https://github.com/advisories/GHSA-9c4g-fp4r-prrv
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/09/GHSA-9c4g-fp4r-prrv/GHSA-9c4g-fp4r-prrv.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-9c4g-fp4r-prrv
Aliases
  • CVE-2025-11148
Published
2025-09-30T12:30:51Z
Modified
2025-10-03T18:22:21Z
Severity
  • 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
  • 9.3 (Critical) CVSS_V4 - 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 CVSS Calculator
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.

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"
}
References

Affected packages

npm / check-branches

Package

Name
check-branches
View open source insights on deps.dev
Purl
pkg:npm/check-branches

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Last Affected
0.0.19

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/09/GHSA-9c4g-fp4r-prrv/GHSA-9c4g-fp4r-prrv.json"