CVE-2026-64648
next: Next.js: Information disclosure via server-side fetch cache
Overview
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 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.
Source: OX vulnerability database
Severity
5.4 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Weakness: CWE-524
Affected packages · 3
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | next | >=13.0.0, <15.5.21>=16.0.0, <16.2.11 | 15.5.2116.2.11 |
| Seal npm | @seal-security/next | >=16.0.6-sp1, <16.0.6-sp999 | 16.0.6-sp999 |
| Seal npm | next | >=16.0.6-sp0, <16.0.6-sp999 | 16.0.6-sp999 |
Open a package to see all its vulnerabilities.
Operating systems · 15 fixes
chainguard 1 release · 9 packages
| Release | Package | Fixed in |
|---|---|---|
| peerdb-ui | 0.37.3-r1 | |
| keep +1 | 0.54.2-r1 | |
| homepage | 1.13.2-r9 | |
| jitsucom-jitsu | 2.11.0-r30 | |
| langfuse-2 | 2.95.12-r35 | |
| langfuse-fips-2 | 2.95.12-r38 |
3 more rows
minimos 1 release · 4 packages
| Release | Package | Fixed in |
|---|---|---|
| peerdb-ui | 0.37.4-r0 | |
| homepage | 2.0.0-r0 | |
| langfuse-3 | 3.224.1-r0 | |
| trigger-dev | 4.5.0-r0 |
wolfi 1 release · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| jitsucom-jitsu | 2.11.0-r30 | |
| langfuse-3 | 3.225.7-r6 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2026-64648
- github.com https://github.com/vercel/next.js
- github.com https://github.com/vercel/next.js/commit/062f66700b52a5d6bba2c0605d55577ab7ad262c
- github.com https://github.com/vercel/next.js/commit/73b94872bc343d09494b50394d8c08eb9fc8e56a
- github.com https://github.com/vercel/next.js/releases/tag/v15.5.21
- github.com https://github.com/vercel/next.js/releases/tag/v16.2.11
- github.com https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2026-64648
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2026-64648
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.