Next.js· ()

This monthVendor security release

Next.js security releases: 16.3.8, 16.3, 15.5

What
Next.js published security fixes. Upgrade to 16.3.8 / 16.3 / 15.5 (whichever matches your branch). Fixes 7 CVEs. Vendor severity: High, Medium, Low.
Fix
Upgrade to 16.3.816.315.5
Why this tier
Vendor security release for server software (most severe: CVE-2026-94483).
Exploited
Not known to be exploited · highest EPSS 0.5%
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.3.8, 16.3, 15.5.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-103004 (and the other 6 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 7#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-94483Routine8.3 (v4.0)0.3%Nonone
CVE-2026-103004Routine6.3 (v4.0)0.3%Nonone
CVE-2026-94484Routine6.3 (v4.0)0.2%Nonone
CVE-2026-94485Routine6.3 (v4.0)0.2%Nonone
CVE-2026-94543Routine6.3 (v4.0)0.5%Nonone
CVE-2026-94544Routine6.3 (v4.0)0.2%Nonone
CVE-2026-94486Routine2.3 (v4.0)0.1%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.