Bug 2545233 (CVE-2026-94543)

Summary: CVE-2026-94543 next: Next.js: Response cache poisoning via improper route binding
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bbrownin, eborisov, gotiwari, jhorak, kaycoth, lball, mvyas, ngough, rhel-process-autobot, veshanka, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Next.js. In self-hosted applications using the Pages Router with static generation or Incremental Static Regeneration (ISR), response cache entries are not sufficiently bound to their source route. A remote attacker can exploit this issue by sending crafted requests to replace a page's cache entry with content from a different route. This results in response cache poisoning, causing the application to serve incorrect content to subsequent visitors.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2558974, 2558977, 2558978, 2558980, 2558981, 2558975, 2558982    
Bug Blocks:    

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.