Next.js· ()

This monthVendor security release

Next.js security releases: 16.2.11, 15.5.21

What
Next.js published security fixes. Upgrade to 16.2.11 / 15.5.21 (whichever matches your branch). Fixes 9 CVEs. Vendor severity: High, Medium.
Fix
Upgrade to 16.2.1115.5.21
Why this tier
Vendor security release for server software (most severe: CVE-2026-64642).
Exploited
Not known to be exploited · highest EPSS 0.9%
Share this

What to do now#

  1. Check whether you run an affected Next.js version:
    npx next --version
  2. Upgrade to the fixed release for your branch: 16.2.11, 15.5.21.Vendor announcement
  3. Bump next in package.json, rebuild and redeploy. Apps hosted on Vercel may already be protected at the platform, but self-hosted ones are not.
  4. Using distro packages? Distros backport fixes under their own version numbers. Check your distro's status for CVE-2026-64641 (and the other 8 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 9#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-64642Routine8.3 (v4.0)0.6%Nonone
CVE-2026-64641Routine8.2 (v4.0)0.9%Nonone
CVE-2026-64645Routine8.3 (v4.0)0.5%Nonone
CVE-2026-64649Routine8.3 (v4.0)0.5%Nonone
CVE-2026-64644Routine6.3 (v4.0)0.7%Nonone
CVE-2026-64643Routine6.3 (v4.0)0.5%Nonone
CVE-2026-64646Routine6.3 (v4.0)0.5%Nonone
CVE-2026-64647Routine6.3 (v4.0)0.4%Nonone
CVE-2026-64648Routine6.0 (v4.0)0.4%Nonone

Sources#

Built from Next.js: GitHub Security Advisories (vercel/next.js), checked . Tier from the published rubric.

Also on today's list

See today's list → · Coming up →

Something wrong on this page?
Anonymous. Reports are checked against the primary source.