Bug 2477211 (CVE-2026-44582) - CVE-2026-44582 Next.js: Next.js: Cache poisoning allows incorrect response delivery
Summary: CVE-2026-44582 Next.js: Next.js: Cache poisoning allows incorrect response de...
Keywords:
Status: NEW
Alias: CVE-2026-44582
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2484214 2484216 2484218 2484210 2484212 2484220 2484222
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-13 18:02 UTC by OSIDB Bzimport
Modified: 2026-07-05 08:33 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-13 18:02:56 UTC
Next.js is a React framework for building full-stack web applications. From 13.4.6 to before 15.5.16 and 16.2.5, React Server Component responses can be vulnerable to cache poisoning in deployments that rely on shared caches with insufficient response partitioning. In affected conditions, collisions in the _rsc cache-busting value can allow an attacker to poison cache entries so users receive the wrong response variant for a given URL. This vulnerability is fixed in 15.5.16 and 16.2.5.


Note You need to log in before you can comment on or make changes to this bug.