next
Affected
- introduced
13.0.0, fixed15.5.21(semver)
Fixed versions
15.5.21
Fix
- Fixed version
15.5.21npm install [email protected]
Advisory
Also known as: CVE-2026-64647
Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
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.
Medium Basis: The source's own band: MODERATE
13.0.0, fixed 15.5.21 (semver)15.5.21
15.5.21npm install [email protected]16.0.0, fixed 16.2.11 (semver)16.2.11
16.2.11npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0