Bug 2545233 (CVE-2026-94543) - CVE-2026-94543 next: Next.js: Response cache poisoning via improper route binding
Summary: CVE-2026-94543 next: Next.js: Response cache poisoning via improper route bin...
Keywords:
Status: NEW
Alias: CVE-2026-94543
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2558974 2558977 2558978 2558980 2558981 2558975 2558982
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-02 15:36 UTC by OSIDB Bzimport
Modified: 2026-10-29 16:20 UTC (History)
11 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-02 15:36:09 UTC
Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, self-hosted applications using the Pages Router with statically generated or Incremental Static Regeneration pages can key a response cache entry without sufficiently binding it to the source route. A request can replace one page's cache entry with content from a different route, causing the affected page to serve incorrect content to every visitor until revalidation. Applications deployed on Vercel are not affected. This issue is fixed in versions 15.5.27 and 16.3.8.


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