npm package
cookie vulnerabilities by version
The latest release, 2.0.1 (Jun 30, 2026), has no known vulnerabilities. 10% of last week’s 231.4M downloads went to versions with known vulnerabilities. OSV.dev lists 1 advisory for cookie; the newest was published on Oct 4, 2024.
npm (opens in a new tab) describes it as “HTTP server cookie parsing and serialization”
- Latest release
- 2.0.1
- Jun 30, 2026, no known vulnerabilities
- Downloads last week
- 231.4M
- All versions, from npm
- Advisories on OSV.dev
- 1
- Newest Oct 4, 2024
- Licence
- MIT
Most-downloaded versions last week
From npm’s per-version download counts for the last 7 days, each checked against OSV.dev. Open a version for its advisories and what to upgrade to.
Who is still on a vulnerable cookie
10% of last week’s 231.4M cookie downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Release lines
The newest release of each major line, from the registry. cookie doesn’t publish support dates we can check.
Newest advisories
The 1 most recently published, with the versions each one affects.
LowCVE-2024-47764 on OSV.dev (opens in a new tab)GHSA-pxg6-pf52-xh8x
cookie accepts cookie name, path, and domain with out of bounds characters
Affects < 0.7.0. Published Oct 4, 2024.
Which cookie do you have?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task for your coding agent. Free, no sign-up.
How this page is checked
StackPrism reads every OSV.dev advisory for cookie, merges duplicates filed under several ids, and asks OSV.dev which ones affect each version listed. Releases and their dates come from deps.dev, downloads from npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.