What is GHSA-JJMG-X456-W976?

GHSA-JJMG-X456-W976 is a low-severity security vulnerability in csrf-csrf (npm), affecting versions < 2.2.1. It is fixed in 2.2.1.

Which versions of csrf-csrf are affected by GHSA-JJMG-X456-W976?

csrf-csrf (npm) versions < 2.2.1 is affected.

Is there a fix for GHSA-JJMG-X456-W976?

Yes. GHSA-JJMG-X456-W976 is fixed in 2.2.1. Upgrade to this version or later.

Is GHSA-JJMG-X456-W976 exploitable, and should I be worried?

Whether GHSA-JJMG-X456-W976 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-JJMG-X456-W976 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-JJMG-X456-W976?

Upgrade csrf-csrf to 2.2.1 or later.

GHSA-JJMG-X456-W976 in csrf-csrf

Q: Which versions of csrf-csrf are affected by GHSA-JJMG-X456-W976?

csrf-csrf (npm) versions < 2.2.1 is affected.

Q: Is there a fix for GHSA-JJMG-X456-W976?

Yes. GHSA-JJMG-X456-W976 is fixed in 2.2.1. Upgrade to this version or later.

Q: Is GHSA-JJMG-X456-W976 exploitable, and should I be worried?

Whether GHSA-JJMG-X456-W976 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-JJMG-X456-W976 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-JJMG-X456-W976?

Upgrade csrf-csrf to 2.2.1 or later.

Summary

Incorrect default cookie name and recommendation

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

You can work around this by providing a custom cookieName as part of the options, which is correctly prefixed with __Host-.

References

Are there any links users can visit to find out more?

https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#cookie-with-__host-prefix

For more information

If you have any questions or comments about this advisory:

Reach out on the Psifi Solutions Discord in the #psifi-support channel

Impact

What kind of vulnerability is it? Who is impacted?

The default cookie name (and documentation recommendation) was prefixed with Host__ instead of __Host-. The point of this prefix is for additional security, to ensure that, when no domain option is provided in the cookie options, we can guarantee the cookie came from the correct domain.

Affected versions

csrf-csrf (< 2.2.1)

Security releases

csrf-csrf → 2.2.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

Has the problem been patched? What versions should users upgrade to?

Yes, the problem is patched from version 2.2.1, this will not be back ported, but you can use the workaround described below.

Frequently Asked Questions

What is GHSA-JJMG-X456-W976? GHSA-JJMG-X456-W976 is a low-severity security vulnerability in csrf-csrf (npm), affecting versions < 2.2.1. It is fixed in 2.2.1.
Which versions of csrf-csrf are affected by GHSA-JJMG-X456-W976? csrf-csrf (npm) versions < 2.2.1 is affected.
Is there a fix for GHSA-JJMG-X456-W976? Yes. GHSA-JJMG-X456-W976 is fixed in 2.2.1. Upgrade to this version or later.
Is GHSA-JJMG-X456-W976 exploitable, and should I be worried? Whether GHSA-JJMG-X456-W976 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-JJMG-X456-W976 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-JJMG-X456-W976? Upgrade csrf-csrf to 2.2.1 or later.