GHSA-jjmg-x456-w976
Incorrect default cookie name and recommendation
Blast Radius
csrf-csrfReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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.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. 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 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 pinpoints whether GHSA-jjmg-x456-w976 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-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 detects GHSA-jjmg-x456-w976 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.