What is GHSA-HXWM-X553-X359?

GHSA-HXWM-X553-X359 is a medium-severity OS command injection vulnerability in @npmcli/git (npm), affecting versions < 2.0.8. It is fixed in 2.0.8. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

Which versions of @npmcli/git are affected by GHSA-HXWM-X553-X359?

@npmcli/git (npm) versions < 2.0.8 is affected.

Is there a fix for GHSA-HXWM-X553-X359?

Yes. GHSA-HXWM-X553-X359 is fixed in 2.0.8. Upgrade to this version or later.

Is GHSA-HXWM-X553-X359 exploitable, and should I be worried?

Whether GHSA-HXWM-X553-X359 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-HXWM-X553-X359 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-HXWM-X553-X359?

Upgrade @npmcli/git to 2.0.8 or later.

GHSA-HXWM-X553-X359 in @npmcli/git

Q: Which versions of @npmcli/git are affected by GHSA-HXWM-X553-X359?

@npmcli/git (npm) versions < 2.0.8 is affected.

Q: Is there a fix for GHSA-HXWM-X553-X359?

Yes. GHSA-HXWM-X553-X359 is fixed in 2.0.8. Upgrade to this version or later.

Q: Is GHSA-HXWM-X553-X359 exploitable, and should I be worried?

Whether GHSA-HXWM-X553-X359 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-HXWM-X553-X359 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-HXWM-X553-X359?

Upgrade @npmcli/git to 2.0.8 or later.

Summary

Arbitrary Command Injection due to Improper Command Sanitization

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.

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.

Acknowledgements

This report was reported to us by @tyage (Ierae Security) through the GitHub Bug Bounty Program.

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

Affected versions

@npmcli/git (< 2.0.8)

Security releases

@npmcli/git → 2.0.8 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This issue has been patched in release 2.0.8

Frequently Asked Questions

What is GHSA-HXWM-X553-X359? GHSA-HXWM-X553-X359 is a medium-severity OS command injection vulnerability in @npmcli/git (npm), affecting versions < 2.0.8. It is fixed in 2.0.8. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
Which versions of @npmcli/git are affected by GHSA-HXWM-X553-X359? @npmcli/git (npm) versions < 2.0.8 is affected.
Is there a fix for GHSA-HXWM-X553-X359? Yes. GHSA-HXWM-X553-X359 is fixed in 2.0.8. Upgrade to this version or later.
Is GHSA-HXWM-X553-X359 exploitable, and should I be worried? Whether GHSA-HXWM-X553-X359 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-HXWM-X553-X359 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-HXWM-X553-X359? Upgrade @npmcli/git to 2.0.8 or later.