VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

cookie: vulnerability history, versions and safety

cookie is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 25 releases, first recorded in Oct 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded L2
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 cookie vulnerabilities

Vulert verdict on cookie 2.0.1 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2.0.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 04 Oct 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 5,818 packages i
  • Stars 1,536 i
  • OpenSSF scorecard 6/10 i
  • Last release 3 months ago i
  • Licence MIT 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 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
2.0.1 30 Jun 2026 none MIT — Details →
2.0.0 24 Jun 2026 none MIT — Details →
1.1.1 26 Nov 2025 none MIT — Details →
1.1.0 25 Nov 2025 none MIT — Details →
1.0.2 20 Nov 2024 none MIT — Details →
1.0.1 11 Oct 2024 none MIT — Details →
1.0.0 08 Oct 2024 none MIT — Details →
0.7.2 07 Oct 2024 none MIT — Details →
0.7.1 03 Oct 2024 none MIT — Details →
0.7.0 02 Oct 2024 none MIT — Details →
0.6.0 07 Nov 2023 L2 MIT Yes Details →
0.5.0 11 Apr 2022 L2 MIT Yes Details →
0.4.2 02 Feb 2022 L2 MIT Yes Details →
0.4.1 22 Apr 2020 L2 MIT Yes Details →
0.4.0 16 May 2019 L2 MIT Yes Details →
0.3.1 27 May 2016 L2 MIT Yes Details →
0.3.0 27 May 2016 L2 MIT Yes Details →
0.2.4 21 May 2016 L2 MIT Yes Details →
0.2.3 26 Oct 2015 L2 MIT Yes Details →
0.2.2 17 Sep 2015 L2 MIT Yes Details →
0.1.5 17 Sep 2015 L2 MIT Yes Details →
0.2.1 17 Sep 2015 L2 MIT Yes Details →
0.1.4 17 Sep 2015 L2 MIT Yes Details →
0.2.0 14 Aug 2015 L2 MIT Yes Details →
0.1.3 20 May 2015 L2 MIT Yes Details →
0.1.2 16 Apr 2014 L2 MIT Yes Details →
0.1.1 23 Feb 2014 L2 MIT Yes Details →
0.1.0 01 May 2013 L2 MIT Yes Details →
0.0.6 09 Apr 2013 L2 MIT Yes Details →
0.0.5 29 Oct 2012 L2 MIT Yes Details →
0.0.4 21 Jun 2012 L2 MIT Yes Details →
0.0.3 06 Jun 2012 L2 MIT Yes Details →
0.0.2 01 Jun 2012 L2 MIT Yes Details →
0.0.1 29 May 2012 L2 MIT Yes Details →
0.0.0 28 May 2012 L2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for cookie

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 cookie

Is cookie safe to use?

Vulert records 2 vulnerabilities for cookie in npm: 0 critical, 0 high, 0 medium and 2 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 cookie's Vulert package health score?

Vulert scores cookie 87/100, which reads as healthy. 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 cookie affected?

No. 2.0.1, 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 cookie should I use?

2.0.1 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 cookie have?

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

How often are new cookie vulnerabilities disclosed?

0 vulnerabilities were recorded for cookie in the last 12 months, and the oldest entry in this database dates to 04 Oct 2024. 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 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 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.