Next.js· ()

This monthVendor security release

Next.js security fixes: 3 CVEs

What
Next.js published security fixes across 16 versions; see the fixed versions below. Fixes 3 CVEs. Vendor severity: High, Medium.
Fix
Upgrade to 16.0.1016.0.915.5.915.5.815.4.1015.4.915.3.815.3.715.2.815.2.715.1.1115.1.1015.0.715.0.614.2.3514.2.34
Why this tier
CVE-2025-55184: Public proof-of-concept exists (SSVC exploitation: poc).
Exploited
Not known to be exploited · highest EPSS 64%
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.0.10, 16.0.9, 15.5.9, 15.5.8, 15.4.10, 15.4.9, 15.3.8, 15.3.7, 15.2.8, 15.2.7, 15.1.11, 15.1.10, 15.0.7, 15.0.6, 14.2.35, 14.2.34.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-2025-55183 (and the other 2 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 3#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2025-55184This month7.5 (v3.1)64%Nopoc
CVE-2025-55183This month5.3 (v3.1)64%Nopoc
CVE-2025-67779This month7.5 (v3.1)15%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.