GHSA-jjmg-x456-w976
Incorrect default cookie name and recommendation
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
What each source reports
GitHub AdvisoriesNo score
Incorrect default cookie name and recommendation
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
- Record
GHSA-jjmg-x456-w976- Updated
- 2026-11-02
OSVNo score
Incorrect default cookie name and recommendation
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
- Record
GHSA-jjmg-x456-w976- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
csrf-csrfnpm | before 2.2.1 | 2.2.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-jjmg-x456-w976 is a vulnerability with no CVSS score yet in csrf-csrf, published October 10, 2022. No source lists public exploit code. Fixed in csrf-csrf 2.2.1.