What is GHSA-JMQM-F2GX-4FJV?

GHSA-JMQM-F2GX-4FJV is a medium-severity cross-site request forgery (CSRF) vulnerability in npm-registry-fetch (npm), affecting versions < 4.0.5. It is fixed in 4.0.5, 8.1.1. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.

How severe is GHSA-JMQM-F2GX-4FJV?

GHSA-JMQM-F2GX-4FJV has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of npm-registry-fetch are affected by GHSA-JMQM-F2GX-4FJV?

npm-registry-fetch (npm) versions < 4.0.5 is affected.

Is there a fix for GHSA-JMQM-F2GX-4FJV?

Yes. GHSA-JMQM-F2GX-4FJV is fixed in 4.0.5, 8.1.1. Upgrade to this version or later.

Is GHSA-JMQM-F2GX-4FJV exploitable, and should I be worried?

Whether GHSA-JMQM-F2GX-4FJV 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-JMQM-F2GX-4FJV 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.

GHSA-JMQM-F2GX-4FJV in npm-registry-fetch

Q: How severe is GHSA-JMQM-F2GX-4FJV?

GHSA-JMQM-F2GX-4FJV has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of npm-registry-fetch are affected by GHSA-JMQM-F2GX-4FJV?

npm-registry-fetch (npm) versions < 4.0.5 is affected.

Q: Is there a fix for GHSA-JMQM-F2GX-4FJV?

Yes. GHSA-JMQM-F2GX-4FJV is fixed in 4.0.5, 8.1.1. Upgrade to this version or later.

Q: Is GHSA-JMQM-F2GX-4FJV exploitable, and should I be worried?

Whether GHSA-JMQM-F2GX-4FJV 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-JMQM-F2GX-4FJV 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-JMQM-F2GX-4FJV?

Upgrade: npm-registry-fetch to 4.0.5 or later, npm-registry-fetch to 8.1.1 or later.

Summary

Sensitive information exposure through logs in npm-registry-fetch

Affected versions of npm-registry-fetch are vulnerable to an information exposure vulnerability through log files. The cli supports URLs like <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>. The password value is not redacted and is printed to stdout and also to any generated log files.

Impact

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

GHSA-JMQM-F2GX-4FJV has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.5, 8.1.1); upgrading removes the vulnerable code path.

Affected versions

npm-registry-fetch (< 4.0.5) npm-registry-fetch (>= 5.0.0, < 8.1.1)

Security releases

npm-registry-fetch → 4.0.5 (npm) npm-registry-fetch → 8.1.1 (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

Upgrade the following packages to resolve this vulnerability:

npm-registry-fetch to 4.0.5 or later; npm-registry-fetch to 8.1.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-JMQM-F2GX-4FJV? GHSA-JMQM-F2GX-4FJV is a medium-severity cross-site request forgery (CSRF) vulnerability in npm-registry-fetch (npm), affecting versions < 4.0.5. It is fixed in 4.0.5, 8.1.1. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
How severe is GHSA-JMQM-F2GX-4FJV? GHSA-JMQM-F2GX-4FJV has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of npm-registry-fetch are affected by GHSA-JMQM-F2GX-4FJV? npm-registry-fetch (npm) versions < 4.0.5 is affected.
Is there a fix for GHSA-JMQM-F2GX-4FJV? Yes. GHSA-JMQM-F2GX-4FJV is fixed in 4.0.5, 8.1.1. Upgrade to this version or later.
Is GHSA-JMQM-F2GX-4FJV exploitable, and should I be worried? Whether GHSA-JMQM-F2GX-4FJV 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-JMQM-F2GX-4FJV 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-JMQM-F2GX-4FJV?
- Upgrade npm-registry-fetch to 4.0.5 or later
- Upgrade npm-registry-fetch to 8.1.1 or later