npm package

cookie 0.3.0 vulnerability, and the version that fixes it

cookie 0.3.0 has 1 known vulnerability; 0.7.0 fixes it.

npm (opens in a new tab) describes it as “HTTP server cookie parsing and serialization”

Known vulnerabilities
1
None rated high or critical
Released
May 27, 2016
Latest is 2.0.1
Downloads last week
60
Under 1% of cookie downloads
Licence
MIT
OpenSSF Scorecard
8.2/10
jshttp/cookie (opens in a new tab)
Dependencies
None
Resolved by deps.dev

What to upgrade to

0.7.0 is the closest release with no known vulnerabilities.

  • 0.3.1

    Newest 0.3.x release. Released May 27, 2016.

    1 known vulnerability, worst rated warning
  • 0.7.0Upgrade to this

    Fixes the known vulnerability. Released Oct 2, 2024.

    No known vulnerabilities
  • 2.0.1

    Latest release. Released Jun 30, 2026.

    No known vulnerabilities

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Every advisory for cookie 0.3.0

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. LowCVE-2024-47764 on OSV.dev (opens in a new tab)GHSA-pxg6-pf52-xh8xEPSS: top 47%

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

    Fixed in 0.7.0. Published Oct 4, 2024.

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.

Is cookie the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly cookie 0.3.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.