GHSA-jjmg-x456-w976 — csrf-csrf
Fix: Psifi-Solutions/csrf-csrf@8f1ce8dGHSA-jjmg-x456-w976 is a security vulnerability in csrf-csrf. A fix is available for csrf-csrf — see the affected versions and patch details below.
Incorrect default cookie name and recommendation
Real-World Exposure
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.
csrf-csrfnpmDescription
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.
Patches
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.
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?
For more information
If you have any questions or comments about this advisory:
- Reach out on the Psifi Solutions Discord in the
#psifi-supportchannel
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | csrf-csrf | all versions | 2.2.1npm install csrf-csrf@2.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for csrf-csrf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update csrf-csrf to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jjmg-x456-w976 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jjmg-x456-w976 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jjmg-x456-w976. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jjmg-x456-w976 in your dependencies?
O3 Security finds GHSA-jjmg-x456-w976 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.