ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-64648

Cache confusion of response bodies for requests with bodies

Published Jul 21, 2026 · catalog updated Jul 21, 2026 · Cache confusion of response

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-64648. EPSS is 0.34%. Act only if a listed version of Cache confusion of response is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Cache confusion of response).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.34%
Remediation
Version ranges on file
Affected products
npm next

## Impact A server-side 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 's **response** body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to calls with a request that has a different init than the one passed to . Safe: Unsafe: ## Workarounds No workaround exists besides upgrading. Applications using Pages Router are not vulnerable.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm next >= 16.0.0 < 16.2.11
  • npm next>=13.0.0 < 15.5.21

How to fix CVE-2026-64648

  • Upgrade

    CVE-2026-64648 lists a fix boundary at 16.2.11. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in >= 16.0.0 < 16.2.11 · 1 other packages on the advisory

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-64648. EPSS is 0.34%. Act only if a listed version of Cache confusion of response is installed.

Which versions are affected?

Compare what you have installed with >= 16.0.0 < 16.2.11, >=13.0.0 < 15.5.21. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Next.js security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 21, 2026 · Maintainer security tabs

    Detected

    ## Impact A server-side 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 's **response** body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to calls with a request that has a different init than the one passed to . Safe: Unsafe: ## Workarounds

Sources

  • Maintainer security tabsVendor advisoryGHSA-68g3-v927-f742

    ## Impact A server-side 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 's **response** body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to calls with a request that has a different init than the one passed to . Safe: Unsafe: ## Workarounds

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026