interactive-git-checkout has a Command Injection vulnerability
CVE-2025-59046GHSA-4wcm-7hjf-6xw5
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm interactive-git-checkout
- Affected
- <= 1.1.4
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-4wcm-7hjf-6xw5 lists affected ranges: npm interactive-git-checkout >=0 <=1.1.4
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4wcm-7hjf-6xw5 lists affected ranges: npm interactive-git-checkout >=0 <=1.1.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2025-59046: 1.19% estimated exploitation activity in the next 30 days; percentile 67.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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. Resources: Project's npm package: https://www.npmjs.com/package/interactive-git-checkout Command Injection Vulnerability The interactive-git-checkout tool is vulnerable to a command injection vulnerability because it 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. The following vulnerable code snippets demonstrates the issue: Exploit Proof of Concept 1. Install the interactive-git-checkout package (as suggested by the package's README): 2. Run the executable exposed by the installed package: 3. When prompted, enter the following branch name: Vulnerable versions All versions of interactive-git-checkout…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-4wcm-7hjf-6xw5
- Revision 1 · created ·
Published from osv record GHSA-4wcm-7hjf-6xw5
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-59046 Advisory: interactive-git-checkout has a Command Injection vulnerability IDs: CVE-2025-59046, GHSA-4wcm-7hjf-6xw5 Record: https://patchnext.com/advisories/cve-2025-59046 (revision 2, source checked 26 Oct 2026, 12:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) 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 interactive-git-checkout: affected <= 1.1.4 ## Suggested inspection (read-only) - `npm ls interactive-git-checkout --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 interactive-git-checkout. - 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-4wcm-7hjf-6xw5 (OSV record GHSA-4wcm-7hjf-6xw5 lists affected ranges: npm interactive-git-checkout >=0 <=1.1.4) - Verified: https://github.com/advisories/GHSA-4wcm-7hjf-6xw5 (GitHub-reviewed advisory GHSA-4wcm-7hjf-6xw5 lists affected ranges: npm interactive-git-checkout >=0 <=1.1.4) Commands are suggestions: review each one before running it.
Loading voting…