StackPrism

npm package

next 15.5.26 vulnerabilities, and the version that fixes all of them

next 15.5.26 has 2 known vulnerabilities; 15.5.27 fixes all of them. Next.js 15 reaches end of life on Oct 21, 2026. Move to Next.js 16 (LTS).

npm (opens in a new tab) describes it as “The React Framework”

Known vulnerabilities
2
None rated high or critical
Released
Sep 22, 2026
Latest is 16.4.2
Downloads last week
1.3M
2% of next downloads
Next.js 15 support
Ending soon
Until Oct 21, 2026
Licence
MIT
OpenSSF Scorecard
6.2/10
vercel/next.js (opens in a new tab)
Pulls in
49 packages
Resolved by deps.dev

What to upgrade to

15.5.27 is the closest release with no known vulnerabilities.

  • 15.5.27Upgrade to this

    Fixes all 2 known vulnerabilities. Released Sep 30, 2026.

    No known vulnerabilities

  • 15.5.28

    Newest 15.x release. Released Oct 14, 2026.

    No known vulnerabilities

  • 16.4.2

    Latest release. Released Oct 15, 2026.

    No known vulnerabilities

15.5.27 came out on Sep 30, 2026. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Every advisory for next 15.5.26

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. WarningCVE-2026-94543 on OSV.dev (opens in a new tab)GHSA-4jqv-mc3x-m676EPSS: top 81%

    Next.js has cache poisoning of SSG and ISR pages in self-hosted applications

    Fixed in 15.5.27. Published Oct 7, 2026.

  2. WarningCVE-2026-94484 on OSV.dev (opens in a new tab)GHSA-mcj8-r9mp-w47pEPSS: top 86%

    Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service

    Fixed in 15.5.27. Published Oct 7, 2026.

Who is still on a vulnerable next

67% of last week’s 67.5M next downloads went to versions with known vulnerabilities.

From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.

Is next the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly next 15.5.26, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm, support dates from endoflife.date. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev, CISA KEV, FIRST EPSS and endoflife.date.