Advisory

GHSA-4633-3j49-mh5q

Also known as: CVE-2026-64647

Summary

Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-07-22 23:06 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

next

npm · All systems

Affected

  • introduced 13.0.0, fixed 15.5.21 (semver)

Fixed versions

15.5.21

Fix

next

npm · All systems

Affected

  • introduced 16.0.0, fixed 16.2.11 (semver)

Fixed versions

16.2.11

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences