Vulnerability Database · npm · cookie · Version
cookie 0.0.2
0.0.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: 2.0.1.
Critical 0 High 0 Medium 0 Low 2 Unrated 0
-
Released 01 Jun 2012
Licence MIT
Also known from other sources 1
Newer releases 35
Database updated 23/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
cookie 0.0.2 vulnerabilities
2 vulnerabilities cover cookie 0.0.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2024-47764: cookie Package Vulnerability Allowing Out of Bounds Characters in Cookie Fields | N/A low | 0.7.0 | 04 Oct 2024 |
| CVE-2024-47764: cookie Package Vulnerability Allows Out of Bounds Characters in Cookie Fields | N/A low | 0.7.0 | 04 Oct 2024 |
Looking for another version, or everything Vulert holds for cookie?
Questions
About cookie 0.0.2
Is cookie 0.0.2 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover cookie 0.0.2: 0 critical, 0 high, 0 medium and 2 low. The upgrade Vulert recommends is 2.0.1, and each entry above names the fixed version to move to.
Which version of cookie should I use instead of 0.0.2?
2.0.1 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 0.0.2 the latest release of cookie?
No. 0.0.2 was published 01 Jun 2012, 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 cookie for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the 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.