VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

tough-cookie: vulnerability history, versions and safety

tough-cookie is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 41 releases, from Jul 2018 to Jul 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tough-cookie vulnerabilities

Vulert verdict on tough-cookie 6.0.2 i

Updated on 22 Oct 2026

Good news: 6.0.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 6.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 6.0.2 — unaffected i
  • Vulnerabilities on record 3 over 4 years · 0 in the last year i
  • Latest disclosure 01 Jul 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 16,250 packages i
  • Stars 1,064 i
  • OpenSSF scorecard 5/10 i
  • Last release 3 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for tough-cookie, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.0.2 07 Jul 2026 none BSD-3-Clause — Details →
6.0.1 12 Mar 2026 none BSD-3-Clause — Details →
6.0.0 14 Aug 2025 none BSD-3-Clause — Details →
6.0.0-rc.2 04 Aug 2025 none BSD-3-Clause — Details →
6.0.0-rc.1 24 Jul 2025 none BSD-3-Clause — Details →
6.0.0-rc.0 02 May 2025 none BSD-3-Clause — Details →
5.1.2 28 Feb 2025 none BSD-3-Clause — Details →
5.1.1 07 Feb 2025 none BSD-3-Clause — Details →
5.1.0 09 Jan 2025 none BSD-3-Clause — Details →
5.1.0-rc.0 08 Jan 2025 none BSD-3-Clause — Details →
5.0.0 09 Sep 2024 none BSD-3-Clause — Details →
5.0.0-rc.4 19 Jul 2024 none BSD-3-Clause — Details →
5.0.0-rc.3 10 Jul 2024 none BSD-3-Clause — Details →
5.0.0-rc.2 16 May 2024 none BSD-3-Clause — Details →
4.1.4 29 Apr 2024 none BSD-3-Clause — Details →
5.0.0-rc.1 29 Feb 2024 none BSD-3-Clause — Details →
5.0.0-rc.0 27 Sep 2023 none BSD-3-Clause — Details →
4.1.3 05 Jun 2023 none BSD-3-Clause — Details →
4.1.2 25 Aug 2022 M1 BSD-3-Clause Yes Details →
4.1.1 24 Aug 2022 M1 BSD-3-Clause Yes Details →
4.1.0 22 Aug 2022 M1 BSD-3-Clause Yes Details →
4.0.0 19 Mar 2020 M1 BSD-3-Clause Yes Details →
3.0.1 05 Feb 2019 M1 BSD-3-Clause Yes Details →
3.0.0 08 Jan 2019 M1 BSD-3-Clause Yes Details →
2.5.0 26 Nov 2018 M1 BSD-3-Clause Yes Details →
2.4.3 25 Jun 2018 M1 BSD-3-Clause Yes Details →
2.4.2 04 Jun 2018 M1 BSD-3-Clause Yes Details →
2.3.4 26 Feb 2018 M1 BSD-3-Clause Yes Details →
2.3.3 21 Sep 2017 M1 BSD-3-Clause Yes Details →
2.3.2 25 Oct 2016 H1 M1 BSD-3-Clause Yes Details →
2.3.1 26 Jul 2016 H1 M1 BSD-3-Clause Yes Details →
2.3.0 21 Jul 2016 H1 M1 BSD-3-Clause Yes Details →
2.2.2 09 Mar 2016 H1 M2 BSD-3-Clause Yes Details →
2.2.1 13 Nov 2015 H1 M2 BSD-3-Clause Yes Details →
2.2.0 06 Oct 2015 H1 M2 BSD-3-Clause Yes Details →
2.1.0 02 Oct 2015 H1 M2 BSD-3-Clause Yes Details →
2.0.0 10 Jun 2015 H1 M2 BSD-3-Clause Yes Details →
1.2.0 25 May 2015 H1 M2 BSD-3-Clause Yes Details →
1.1.0 28 Apr 2015 H1 M2 BSD-3-Clause Yes Details →
1.0.0 28 Apr 2015 H1 M2 BSD-3-Clause Yes Details →
0.13.0 22 Apr 2015 H1 M2 BSD-3-Clause Yes Details →
0.12.1 16 Jan 2014 H1 M2 MIT Yes Details →
0.12.0 13 Jan 2014 H1 M2 MIT Yes Details →
0.11.0 13 Jan 2014 H1 M2 MIT Yes Details →
0.10.0 10 Jan 2014 H1 M2 MIT Yes Details →
0.9.15 25 Jan 2013 H1 M2 BSD-3-Clause Yes Details →
0.9.14 28 Sep 2012 H1 M2 BSD-3-Clause Yes Details →
0.9.13 08 May 2012 H1 M2 BSD-3-Clause Yes Details →
0.9.12 25 Apr 2012 H1 M2 BSD-3-Clause Yes Details →
0.9.11 23 Apr 2012 H1 M2 BSD-3-Clause Yes Details →
0.9.9 17 Apr 2012 H1 M2 BSD-3-Clause Yes Details →
0.9.8 15 Dec 2011 H1 M2 BSD-3-Clause Yes Details →
0.9.7 01 Dec 2011 H1 M2 BSD-3-Clause Yes Details →
0.9.6 23 Nov 2011 H1 M2 BSD-3-Clause Yes Details →
0.9.5 23 Nov 2011 H1 M2 BSD-3-Clause Yes Details →
0.9.4 23 Nov 2011 H1 M2 BSD-3-Clause Yes Details →
0.9.3 07 Nov 2011 H1 M2 BSD-3-Clause Yes Details →
0.9.1 31 Oct 2011 H1 M2 BSD-3-Clause Yes Details →
0.9.0 21 Oct 2011 H1 M2 BSD-3-Clause Yes Details →

All 59 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for tough-cookie

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-15010: Regular Expression Denial of Service in tough-cookie 7.5 high 2.3.3 24 Jul 2018
CVE-2023-26136: Prototype Pollution vulnerability in tough-cookie 6.5 medium 4.1.3 01 Jul 2023
CVE-2016-1000232: ReDoS in tough-cookie 5.3 medium 2.3.0 10 Oct 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524171

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About tough-cookie

Is tough-cookie safe to use?

Vulert records 3 vulnerabilities for tough-cookie in npm: 0 critical, 1 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is tough-cookie's Vulert package health score?

Vulert scores tough-cookie 84/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of tough-cookie affected?

No. 6.0.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of tough-cookie should I use?

6.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does tough-cookie have?

3 vulnerabilities are recorded for tough-cookie in the npm ecosystem: 0 critical, 1 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tough-cookie vulnerabilities disclosed?

0 vulnerabilities were recorded for tough-cookie in the last 12 months, and the oldest entry in this database dates to 24 Jul 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tough-cookie are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tough-cookie for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tough-cookie version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.