Next.js· ()

Patch todayVendor security release

Next.js: RCE in React Server Components

What
Next.js published security fixes across 7 versions; see the fixed versions below. Fixes 1 CVE. Vendor severity: Critical.
Fix
Upgrade to 16.0.715.5.715.4.815.3.615.2.615.1.915.0.5
Why this tier
Known exploited and used in ransomware campaigns.
Exploited
Yes: 1 CVE in CISA KEV · highest EPSS 100%
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.7, 15.5.7, 15.4.8, 15.3.6, 15.2.6, 15.1.9, 15.0.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-2025-55182:Debian · Ubuntu · Red Hat · Alpine
  5. This is exploited in the wild: after patching, check exposed systems for signs of compromise.

CVEs 1#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2025-55182Patch today10.0 (v3.1)100%Yesactive

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.