StackPrism

npm package

next 15.5.28: no known vulnerabilities

next 15.5.28 has no known vulnerabilities in OSV.dev. 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
0
None in OSV.dev
Released
Oct 14, 2026
Latest is 16.4.2
Downloads last week
0
0% 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

Newer releases

15.5.28 has nothing to fix today. Newer releases, for when you upgrade:

  • 16.4.2

    Latest release. Released Oct 15, 2026.

    No known vulnerabilities

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

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.28, 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 and endoflife.date.