StackPrism

npm package

tough-cookie 2.5.0 vulnerability, and the version that fixes it

tough-cookie 2.5.0 has 1 known vulnerability; 4.1.3 fixes it.

npm (opens in a new tab) describes it as “RFC6265 Cookies and Cookie Jar for node.js”

Known vulnerabilities
1
None rated high or critical
Released
Nov 26, 2018
Latest is 6.0.2
Downloads last week
10.5M
7% of tough-cookie downloads
Licence
BSD-3-Clause
OpenSSF Scorecard
6.6/10
salesforce/tough-cookie (opens in a new tab)
Pulls in
2 packages
Resolved by deps.dev

What to upgrade to

4.1.3 is the closest release with no known vulnerabilities.

  • 4.1.3Upgrade to this

    Fixes the known vulnerability. Released Jun 5, 2023.

    No known vulnerabilities

  • 6.0.2

    Latest release. Released Jul 7, 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 tough-cookie 2.5.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. WarningCVE-2023-26136 on OSV.dev (opens in a new tab)GHSA-72xf-g2v4-qvf3EPSS: top 15%

    tough-cookie Prototype Pollution vulnerability

    Fixed in 4.1.3. Published Jul 1, 2023.

Who is still on a vulnerable tough-cookie

12% of last week’s 141.2M tough-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 tough-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 tough-cookie 2.5.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.