Next.js· ()

This monthVendor security release

Next.js security release: 16.3.6

What
Next.js published security fixes. Upgrade to 16.3.6 (whichever matches your branch). Fixes 1 CVE. Vendor severity: Critical.
Fix
Upgrade to 16.3.6
Why this tier
Vendor security release for server software (most severe: CVE-2026-94545).
Exploited
Not known to be exploited · highest EPSS 1.1%
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.6.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-94545:Debian · Ubuntu · Red Hat · Alpine

CVEs 1#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-94545Routine5.3 (v4.0)1.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.