CVE-2026-64648: fallo de gravedad media en vercel next.js
Next.js: Response Body Cache Confusion for Requests Containing Bodies
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 6epss 0.3%
Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to fetch calls with a request that has a different init than the one passed to fetch. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Productos afectados
vercel · next.jsCVEs relacionadas — vercel next.js
En el mismo producto, de las más peligrosas a las menos.
CVE-2025-29927CRITICALAuthorization Bypass in Next.js MiddlewareEPSS 99.2%CVE-2024-46982HIGHCache Poisoning in next.jsEPSS 59.2%CVE-2021-43803HIGHUnexpected server crash in Next.jsEPSS 47.3%CVE-2026-44578HIGHNext.js: Server-side request forgery in applications using WebSocket upgradesEPSS 35.5%CVE-2024-34351HIGHNext.js Server-Side Request Forgery in Server ActionsEPSS 5.5%CVE-2024-51479HIGHAuthorization bypass in Next.jsEPSS 4.0%
Referencias
https://github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad262chttps://github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e56ahttps://github.com/vercel/next.js/releases/tag/v15.5.21https://github.com/vercel/next.js/releases/tag/v16.2.11https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742