En resumen
- CVE-2026-64647 es una vulnerabilidad MEDIO (CVSS 5.4) que afecta a next.js (vercel), next.
- Probabilidad de explotación en los próximos 30 días (EPSS): 0.32%, mayor que el 24.7% de las vulnerabilidades.
- Solución: actualizar a 15.5.21, 16.2.11 o posterior.
| Package | Affected versions | Patched versions |
|---|
| next.js | ≥ 13.0.0, < 15.5.21≥ 16.0.0, < 16.2.11
| 15.5.2116.2.11
|
| next npm | ≥ 13.0.0, < 15.5.21≥ 16.0.0, < 16.2.11
| 15.5.2116.2.11
|
Description
Impact
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 is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache.
Workarounds
If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default in Next.js). Applications using Pages Router are not vulnerable.
NVD description
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 is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache. This issue has been fixed in versions 15.5.21 and 16.2.11.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free