Vulnerability Database · npm · tough-cookie · Version

tough-cookie 2.3.2

2.3.2 is affected by 2 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 6.0.2.

Critical 0 High 1 Medium 1 Low 0 Unrated 0

Released 25 Oct 2016 Licence BSD-3-Clause Also known from other sources 2 Newer releases 59 Database updated 22/Oct/2026

Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version

tough-cookie 2.3.2 vulnerabilities

2 vulnerabilities cover tough-cookie 2.3.2. Open the full list 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

Looking for another version, or everything Vulert holds for tough-cookie?

All versions → Full vulnerability list →

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 →

Questions

About tough-cookie 2.3.2

Is tough-cookie 2.3.2 vulnerable?

Yes. 2 vulnerabilities in the Vulert database cover tough-cookie 2.3.2: 0 critical, 1 high, 1 medium and 0 low. The upgrade Vulert recommends is 6.0.2, and each entry above names the fixed version to move to.

Which version of tough-cookie should I use instead of 2.3.2?

6.0.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 2.3.2 the latest release of tough-cookie?

No. 2.3.2 was published 25 Oct 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.