cookie accepts cookie name, path, and domain with out of bounds characters

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2024-47764: 0.74% estimated exploitation activity in the next 30 days; percentile 54.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, serialize("userName=<scriptalert('XSS3')</script; Max-Age=2592000; a", value) would result in "userName=<scriptalert('XSS3')</script; Max-Age=2592000; a=test", setting userName cookie to <script and ignoring value. A similar escape can be used for path and domain, which could be abused to alter other fields of the cookie. Patches Upgrade to 0.7.0, which updates the validation for name, path, and domain. Workarounds Avoid passing untrusted or arbitrary values for these fields, ensure they are set by the application instead of user input. References https://github.com/jshttp/cookie/pull/167

Published by the source

4 Oct 2024, 20:31 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pxg6-pf52-xh8x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pxg6-pf52-xh8x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-47764

Advisory: cookie accepts cookie name, path, and domain with out of bounds characters
IDs: CVE-2024-47764, GHSA-pxg6-pf52-xh8x
Record: https://patchnext.com/advisories/cve-2024-47764 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: cookie 0.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm cookie: affected < 0.7.0; fixed in 0.7.0

## Suggested inspection (read-only)
- `npm ls cookie --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cookie.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pxg6-pf52-xh8x (OSV record GHSA-pxg6-pf52-xh8x lists affected ranges: npm cookie >=0 <0.7.0 (fixed))
- Verified: https://github.com/advisories/GHSA-pxg6-pf52-xh8x (GitHub-reviewed advisory GHSA-pxg6-pf52-xh8x lists affected ranges: npm cookie >=0 <0.7.0)

Commands are suggestions: review each one before running it.