dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-59046

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The npm package `interactive-git-checkout` is an interactive command-line tool that allows users to checkout a git branch while it prompts for the branch name on the command-line. It is available as an npm package and can be installed via `npm install -g interactive-git-checkout`. Versions up to and including 1.1.4 of the `interactive-git-checkout` tool are vulnerable to a command injection vulnerability because the software passes the branch name to the `git checkout` command using the Node.js child process module's `exec()` function without proper input validation or sanitization. Commit 8dd832dd302af287a61611f4f85e157cd1c6bb41 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The npm package 'interactive-git-checkout' versions 1.1.4 and earlier are vulnerable to command injection. The tool uses Node.js child_process.exec() to pass user-provided branch names directly to the git checkout command without validating or sanitizing the input, allowing attackers to inject arbitrary shell commands via specially crafted branch names.

MitigationUpgrade to the version containing commit 8dd832dd302af287a61611f4f85e157cd1c6bb41 which implements proper input validation/sanitization before passing branch names to exec(). Until upgraded, avoid using the tool with untrusted git repositories or branch names.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if interactive-git-checkout is installed
    Run 'npm list interactive-git-checkout' in your project directory, or check package.json dependencies for this package
    Affected if The package appears in your installed packages or package.json
  2. Identify the installed version
    Run 'npm list interactive-git-checkout --depth=0' to see the exact version number, or check the version field in package.json
    Affected if The version is 1.1.4 or lower (any version from 1.0.0 up to and including 1.1.4)
  3. Locate the vulnerable source code
    Find the package in node_modules and search for files containing 'child_process.exec' or similar patterns - typically in the main entry point or a checkout-related module
    Affected if The package uses child_process.exec() to run git checkout commands with branch name input without sanitization
  4. Confirm the execution pattern
    Examine the code around the exec() call - look for branch names or user input being passed directly as string arguments to exec() without validation
    Affected if Branch names or user input are passed directly to exec() without being sanitized or validated first

You are affected if interactive-git-checkout version 1.1.4 or earlier is installed AND the code uses child_process.exec() with unsanitized branch names.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to the version containing commit 8dd832dd302af287a61611f4f85e157cd1c6bb41 which implements proper input validation/sanitization before passing branch names to exec(). Until upgraded, avoid using the tool with untrusted git repositories or branch names.

Recommended fix High confidence

Version 1.1.5 or later (any version after the vulnerable 1.1.4 release)

  1. Check current installed version: npm list -g interactive-git-checkout
  2. Upgrade to the latest version: npm install -g interactive-git-checkout@latest
  3. Verify the version after upgrade: npm list -g interactive-git-checkout

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59046 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data