vercel · Next.js · published 2026-03-18

CVE-2026-27979Next.js: Unbounded postponed resume buffering can lead to DoS

Routine No exploitation evidence; EPSS 0.8%.

CVE-2026-27979 is not known to be exploited in the wild. EPSS estimates a 0.8% chance of exploitation in the next 30 days, higher than 56% of all CVEs. This Next.js vulnerability: CVSS 6.9 (v4.0), attacks can be automated. Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.1.7, 15.5.14, 15.5.13.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.1.7, 15.5.14, 15.5.13

    Upgrade to 16.1.715.5.1415.5.13

    Why: Vendor security release for server software (most severe: CVE-2026-27979).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.8% (56th pct)FIRST EPSS v2026.06.15
CVSS base score6.9 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Next.js is a React framework for building full-stack web applications. Starting in version 16.0.1 and prior to version 16.1.7, a request containing the `next-resume: 1` header (corresponding with a PPR resume request) would buffer request bodies without consistently enforcing `maxPostponedStateSize` in certain setups. The previous mitigation protected minimal-mode deployments, but equivalent non-minimal deployments remained vulnerable to the same unbounded postponed resume-body buffering behavior. In applications using the App Router with Partial Prerendering capability enabled (via `experimental.ppr` or `cacheComponents`), an attacker could send oversized `next-resume` POST payloads that were buffered without consistent size enforcement in non-minimal deployments, causing excessive memory usage and potential denial of service. This is fixed in version 16.1.7 by enforcing size limits across all postponed-body buffering paths and erroring when limits are exceeded. If upgrading is not immediately possible, block requests containing the `next-resume` header, as this is never valid to be sent from an untrusted client.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

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

Also on today's list

See today's list → · Coming up →