Arbitrary Command Injection due to Improper Command Sanitization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary There exists a command injection vulnerability in npmcli/git versions <2.0.8 which may result in arbitrary shell command execution due to improper argument sanitization when npmcli/git is used to execute Git commands based on user controlled input. The impact of this issue is possible Arbitrary Command Injection when npmcli/git is run with untrusted (user controlled) Git command arguments. Impact Arbitrary Command Injection Details npmcli/git prior to release 2.0.8 passed user controlled input as arguments to a shell command without properly sanitizing this input. Passing unsanitized input to a shell can lead to arbitrary command injection. For example passing git+https://github.com/npm/git; echo hello world would trigger the shell execution of echo hello world. This issue was remediated by no longer running npmcli/git git commands through an intermediate shell. Patches This issue has been patched in release 2.0.8 Acknowledgements This report was reported to us by @tyage…

Published by the source

5 Aug 2021, 17:07 UTC

Last modified by the source

9 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 12:15 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hxwm-x553-x359

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hxwm-x553-x359

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-hxwm-x553-x359

Advisory: Arbitrary Command Injection due to Improper Command Sanitization
IDs: GHSA-hxwm-x553-x359
Record: https://patchnext.com/advisories/ghsa-hxwm-x553-x359 (revision 2, source checked 26 Oct 2026, 12:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @npmcli/git 2.0.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @npmcli/git: affected < 2.0.8; fixed in 2.0.8

## Suggested inspection (read-only)
- `npm ls @npmcli/git --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @npmcli/git.
- 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-hxwm-x553-x359 (OSV record GHSA-hxwm-x553-x359 lists affected ranges: npm @npmcli/git >=0 <2.0.8 (fixed))
- Verified: https://github.com/advisories/GHSA-hxwm-x553-x359 (GitHub-reviewed advisory GHSA-hxwm-x553-x359 lists affected ranges: npm @npmcli/git >=0 <2.0.8)

Commands are suggestions: review each one before running it.