Exploit discussion active in current signal (2 latest mentions)
Recommended action window: High priority (within 72h)
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
| Date | Total | Labels |
|---|
| 2026-07-21 | 1 | Disclosure1 |
| 2026-07-30 | 2 | Disclosure1General1 |
Next.js publicou meu CVE-2026-64648 pra uma falha de cache de confusion https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742
Post summary
The statement reports the publication of CVE-2026-64648, identifying a cache confusion flaw in Next.js, without detailing PoC, exploit, or patch information.
New research published: CVE-2026-64648, discovered by @sybr1d_ in Next.js: https://vyntra.sh/en/research/buglist/CVE-2026-64648?card=2 The issue affected fetch(Request, init) caching: Next.js could generate the cache key from a different request than the one actually sent upstream, allowing a cached POST response associated with one user to be returned to another.
Post summary
New research discloses CVE‑2026‑64648, a cache key generation flaw in Next.js that can leak POST responses between users.
PT: https://vyntra.sh/pt/research/buglist/CVE-2026-64648
Post summary
A link to a Vyntra research page for CVE-2026-64648 is shared, but no explicit details on exploitation, patches, or mitigation steps are provided in the text.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | vercel | next.js | - | node.js | - |