VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

next: vulnerability history, versions and safety

next is a package in the npm ecosystem. Vulert records 77 vulnerabilities for it across 95 releases, from Dec 2017 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
77 vulnerabilities recorded C7 H28 M33 L9
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
48 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all next vulnerabilities

Vulert verdict on next 16.4.2 i

Updated on 22 Oct 2026

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

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

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

  • Current release 16.4.2 — unaffected i
  • Vulnerabilities on record 77 over 8 years · 48 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 1,152 packages i
  • Stars 143,129 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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 next, 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
16.5.0-canary.23 22 Oct 2026 none MIT — Details →
16.5.0-canary.21 20 Oct 2026 none MIT — Details →
16.5.0-canary.20 20 Oct 2026 none MIT — Details →
16.5.0-canary.19 20 Oct 2026 none MIT — Details →
16.5.0-canary.18 19 Oct 2026 none MIT — Details →
16.5.0-canary.17 17 Oct 2026 none MIT — Details →
16.5.0-canary.16 17 Oct 2026 none MIT — Details →
16.5.0-canary.15 15 Oct 2026 none MIT — Details →
16.4.2 15 Oct 2026 none MIT — Details →
16.5.0-canary.14 15 Oct 2026 none MIT — Details →
16.5.0-canary.13 15 Oct 2026 none MIT — Details →
16.5.0-canary.12 14 Oct 2026 none MIT — Details →
16.5.0-canary.11 14 Oct 2026 none MIT — Details →
16.4.1 14 Oct 2026 none MIT — Details →
15.5.28 14 Oct 2026 M2 MIT Yes Details →
16.5.0-canary.10 13 Oct 2026 none MIT — Details →
16.5.0-canary.9 12 Oct 2026 none MIT — Details →
16.5.0-canary.8 10 Oct 2026 none MIT — Details →
16.5.0-canary.7 09 Oct 2026 none MIT — Details →
16.5.0-canary.6 09 Oct 2026 none MIT — Details →
16.5.0-canary.5 09 Oct 2026 none MIT — Details →
16.5.0-canary.4 08 Oct 2026 none MIT — Details →
16.5.0-canary.3 08 Oct 2026 none MIT — Details →
16.5.0-canary.2 07 Oct 2026 none MIT — Details →
16.5.0-canary.1 07 Oct 2026 none MIT — Details →
16.5.0-canary.0 06 Oct 2026 none MIT — Details →
16.4.0 06 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.63 06 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.62 06 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.61 05 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.60 05 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.59 04 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.58 02 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.57 02 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.56 02 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.55 01 Oct 2026 C1 MIT Yes Details →
16.4.0-canary.54 30 Sep 2026 C1 MIT Yes Details →
15.5.27 30 Sep 2026 C1 H1 M2 MIT Yes Details →
16.3.8 30 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.53 30 Sep 2026 C1 MIT Yes Details →
16.3.7 29 Sep 2026 C1 H1 M4 L1 MIT Yes Details →
16.4.0-canary.52 29 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.51 27 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.50 26 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.49 26 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.48 26 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.47 25 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.46 25 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.45 25 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.44 24 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.43 24 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.42 24 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.41 24 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.40 23 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.39 23 Sep 2026 C1 MIT Yes Details →
15.5.26 22 Sep 2026 C1 H1 M3 MIT Yes Details →
16.3.6 22 Sep 2026 C1 H1 M4 L1 MIT Yes Details →
16.4.0-canary.38 22 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.37 19 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.36 18 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.35 17 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.34 16 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.33 16 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.32 15 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.31 14 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.30 14 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.29 14 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.28 12 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.27 11 Sep 2026 C1 MIT Yes Details →
16.3.5 11 Sep 2026 C2 H1 M4 L1 MIT Yes Details →
16.4.0-canary.26 10 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.25 09 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.24 09 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.23 09 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.22 08 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.21 08 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.20 07 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.19 05 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.18 04 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.17 04 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.16 03 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.15 02 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.14 01 Sep 2026 C1 MIT Yes Details →
16.4.0-canary.13 31 Aug 2026 C1 MIT Yes Details →
16.3.4 31 Aug 2026 C2 H1 M4 L1 MIT Yes Details →
15.5.25 31 Aug 2026 C1 H1 M3 MIT Yes Details →
16.4.0-canary.12 29 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.11 28 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.10 28 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.9 27 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.8 25 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.7 25 Aug 2026 C1 MIT Yes Details →
15.5.24 25 Aug 2026 C1 H1 M3 MIT Yes Details →
16.3.3 25 Aug 2026 C2 H1 M4 L1 MIT Yes Details →
16.4.0-canary.6 24 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.5 24 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.4 24 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.3 23 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.2 22 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.1 21 Aug 2026 C1 MIT Yes Details →
16.4.0-canary.0 21 Aug 2026 C1 — Yes Details →
16.3.2 21 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.26 20 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.25 19 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.24 18 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.23 18 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.22 17 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.21 17 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.20 16 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.19 15 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.18 14 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.17 14 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.16 14 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1 13 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.15 13 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.14 12 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.13 12 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.12 11 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.11 11 Aug 2026 C2 H1 M4 L1 — Yes Details →
16.3.1-canary.10 10 Aug 2026 C2 H1 M4 L1 — Yes Details →

The newest 120 of 4,003 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 2
  • 2020 3
  • 2021 3
  • 2022 3
  • 2023 1
  • 2024 6
  • 2025 14
  • 2026 44

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

03 Vulnerabilities

Recorded vulnerabilities for next

The 5 most severe of 77 vulnerabilities recorded for this package

Search all 77 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-66478: Next.js Vulnerable to RCE in React Flight Protocol 10.0 critical 15.0.5 03 Dec 2025
GHSA-673q-mjm6-r5xr: Unauthenticated remote code execution in Next.js cache functions 9.5 critical 16.4.1 22 Oct 2026
Critical Remote Code Execution Vulnerability in Next.js Package 9.5 critical 16.3.6 30 Sep 2026
Critical Unauthenticated Remote Code Execution Vulnerability in Next.js Image Optimization API 9.5 critical 15.5.24 08 Sep 2026
GHSA-2464-fhr4-w9xw: Unauthenticated RCE in Next.js Image Optimization API 9.5 critical 15.5.28 22 Oct 2026

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: 524173

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 next

Is next safe to use?

Vulert records 77 vulnerabilities for next in npm: 7 critical, 28 high, 33 medium and 9 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 next's Vulert package health score?

Vulert scores next 63/100, which reads as usable, but worth attention. 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 next affected?

No. 16.4.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.

How many vulnerabilities does next have?

77 vulnerabilities are recorded for next in the npm ecosystem: 7 critical, 28 high, 33 medium and 9 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new next vulnerabilities disclosed?

48 vulnerabilities were recorded for next in the last 12 months, and the oldest entry in this database dates to 05 Dec 2017. 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 next 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 next for upcoming vulnerabilities?

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