p PatchFirst

CVE-2026-64648

CVE-2026-64648 · Next.js: Response Body Cache Confusion for Requests Containing Bodies

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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 6.0 · Medium · EPSS 0.3% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • next.js

    Versions
    • >= 13.0.0, < 15.5.21: Affected
    • >= 16.0.0, < 16.2.11: Affected

    No fix published

  • next npm

    Affected ranges
    • SEMVER: ≥ 13.0.0, < 15.5.21

    Update to 15.5.21

  • next npm

    Affected ranges
    • SEMVER: ≥ 16.0.0, < 16.2.11

    Update to 16.2.11

Original sources

Check your server →