How severe is GHSA-hxwm-x553-x359?

No CVSS score has been assigned to GHSA-hxwm-x553-x359 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hxwm-x553-x359?

GHSA-hxwm-x553-x359 affects the following packages: @npmcli/git (npm). Ecosystems affected: npm.

How do I fix GHSA-hxwm-x553-x359?

Update @npmcli/git to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxwm-x553-x359 is resolved across your whole dependency graph.

How do I detect GHSA-hxwm-x553-x359 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @npmcli/git. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hxwm-x553-x359 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hxwm-x553-x359?

O3 pinpoints whether GHSA-hxwm-x553-x359 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hxwm-x553-x359 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hxwm-x553-x359 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hxwm-x553-x359 published, and has it been updated?

GHSA-hxwm-x553-x359 was published on August 5, 2021 and was last updated on August 2, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-hxwm-x553-x359

Fix: npm/git#29

GHSA-hxwm-x553-x359 is a remote code execution vulnerability in @npmcli/git. O3 Security confirms whether GHSA-hxwm-x553-x359 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arbitrary Command Injection due to Improper Command Sanitization

Published

Aug 5, 2021

Updated

Aug 2, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 2, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

14other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@npmcli/gitnpm

16.0Mdownloads / week

Description

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 (Ierae Security) through the GitHub Bug Bounty Program.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@npmcli/git`	all versions	2.0.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @npmcli/git. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @npmcli/git to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxwm-x553-x359 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hxwm-x553-x359 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hxwm-x553-x359. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-hxwm-x553-x359 in your dependencies?

O3 detects GHSA-hxwm-x553-x359 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works