StackPrism

npm package

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

next 9.5.0 has 9 known vulnerabilities (1 rated high or critical); 15.5.13 fixes all of them. 15.5.13 has 27 known vulnerabilities of its own, so upgrade to 16.4.2, which has none. Next.js 9 reached end of life on Oct 27, 2020 and gets no more security fixes. Move to Next.js 16 (LTS).

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

Known vulnerabilities
9
1 rated high or critical
Released
Jul 27, 2020
Latest is 16.4.2
Downloads last week
224
Under 1% of next downloads
Next.js 9 support
End of life
Since Oct 27, 2020
Licence
MIT
OpenSSF Scorecard
6.2/10
vercel/next.js (opens in a new tab)
Pulls in
895 packages
Resolved by deps.dev

What to upgrade to

16.4.2 is the closest release with no known vulnerabilities that we checked.

  • 9.5.5

    Newest 9.x release. Released Oct 10, 2020.

    9 known vulnerabilities, worst rated warning

  • 15.5.13

    Fixes all 9 known vulnerabilities. Released Mar 16, 2026.

    27 known vulnerabilities, worst rated warning

  • 16.4.2Upgrade to this

    Latest release. Released Oct 15, 2026.

    No known vulnerabilities

16.4.2 came out on Oct 15, 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 9.5.0

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. CriticalCVE-2021-43803 on OSV.dev (opens in a new tab)GHSA-25mp-g6fv-mqxxEPSS: top 2%

    Unexpected server crash in Next.js.

    Fixed in 11.1.3. Published Dec 7, 2021.

  2. WarningCVE-2025-57822 on OSV.dev (opens in a new tab)GHSA-4342-x723-ch2fEPSS: top 16%

    Next.js Improper Middleware Redirect Handling Leads to SSRF

    Fixed in 14.2.32. Published Aug 29, 2025.

  3. LowCVE-2023-46298 on OSV.dev (opens in a new tab)GHSA-c59h-r6p8-q9wcEPSS: top 31%

    Next.js missing cache-control header may lead to CDN caching empty reply

    Fixed in 13.4.20-canary.13. Published Oct 22, 2023.

  4. WarningCVE-2021-37699 on OSV.dev (opens in a new tab)GHSA-vxf5-wxwp-m7g9EPSS: top 37%

    Open Redirect in Next.js

    Fixed in 11.1.0. Published Aug 12, 2021.

  5. LowCVE-2025-32421 on OSV.dev (opens in a new tab)GHSA-qpjv-v59x-3qc4EPSS: top 45%

    Next.js Race Condition to Cache Poisoning

    Fixed in 14.2.24. Published May 15, 2025.

  6. WarningCVE-2020-15242 on OSV.dev (opens in a new tab)GHSA-x56p-c8cg-q435EPSS: top 46%

    Open Redirect in Next.js versions

    Fixed in 9.5.4. Published Oct 8, 2020.

  7. WarningCVE-2025-55173 on OSV.dev (opens in a new tab)GHSA-xv57-4mr9-wg8vEPSS: top 53%

    Next.js Content Injection Vulnerability for Image Optimization

    Fixed in 14.2.31. Published Aug 29, 2025.

  8. WarningCVE-2026-29057 on OSV.dev (opens in a new tab)GHSA-ggv3-7p47-pfv8EPSS: top 56%

    Next.js: HTTP request smuggling in rewrites

    Fixed in 15.5.13. Published Mar 17, 2026.

  9. WarningCVE-2025-57752 on OSV.dev (opens in a new tab)GHSA-g5qg-72qw-gw5vEPSS: top 74%

    Next.js Affected by Cache Key Confusion for Image Optimization API Routes

    Fixed in 14.2.31. Published Aug 29, 2025.

Who is still on a vulnerable next

59% of last week’s 41M 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 9.5.0, 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.