Skip to main content
VulnerabilityPublished

CVE-2026-44572: vercel next.js · Acceptance of Extraneous Untrusted Data With Trusted Data

Affects vercel next.jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low : upgrade to 16.2.5 or 15.5.16 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 16.2.5, 15.5.16
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade vercel next.js to 16.2.5 or 15.5.16.

Affected software

ProductAffectedFixed in
vercelnext.jsAffected
  • >=16.0.0 <16.2.5
Fixed in
  • 16.2.5
vercelnext.jsAffected
  • >=12.2.0 <15.5.16
Fixed in
  • 15.5.16

AI-suggested

This vulnerability is fixed in Next.js versions 15.5.16 and 16.2.5. Users should upgrade to at least these versions to remediate the issue. If upgrading immediately is not possible, ensure that caching CDNs or reverse proxies vary cache entries based on the x-nextjs-data header or disable caching of 3xx redirect responses on affected paths to prevent cache poisoning. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the fixed versions are clearly identified. Check the Next.js official release notes for confirmation and additional guidance.

Description

Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, an external client could send a x-nextjs-data header on a normal request to a path handled by middleware that returns a redirect. When that happened, the middleware/proxy could treat the request as a data request and replace the standard Location redirect header with the internal x-nextjs-redirect header. Browsers do not follow x-nextjs-redirect, so the response became an unusable redirect for normal clients. If the application was deployed behind a CDN or reverse proxy that caches 3xx responses without varying on this header, a single attacker request could poison the cached redirect response for the affected path. Subsequent visitors could then receive a cached redirect response without a Location header, causing a denial of service for that redirect path until the cache entry expired or was purged. This vulnerability is fixed in 15.5.16 and 16.2.5.

References

Community reviews

Loading reviews…