CVE-2026-94543

Analyzed Analyzed - Analysis Complete

Cache Key Confusion in Next.js Pages Router

Publication date: 2026-10-02

Last updated on: 2026-10-06

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-02

Last Modified

2026-10-06

Generated

2026-10-19

AI Q&A

2026-10-02

EPSS Evaluated

2026-10-18

NVD

CVE-2026-94543

EUVD

EUVD-2026-91670

Affected Vendors & Products

Vendor	Product	Version / Range
vercel	next.js	From 15.0.0 (inc) to 15.5.27 (exc)
vercel	next.js	From 16.0.0 (inc) to 16.3.8 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-524	The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.

Attack-Flow Graph

Executive Summary

This vulnerability affects self-hosted Next.js applications using the Pages Router with statically generated or incrementally regenerated pages. It allows an attacker to replace a page's cache entry with content from a different route, causing the affected page to serve incorrect content to all visitors until the cache is revalidated. Applications hosted on Vercel are not impacted.

Detection Guidance

Detecting this vulnerability requires checking if your Next.js application is running a vulnerable version (15.0.0 to 15.5.27 or 16.3.8) and if it uses Pages Router with SSG or ISR pages. Inspect your package.json for Next.js version and review server logs for unexpected cache behavior or content served from incorrect routes.

Impact Analysis

The primary impact is on the availability of the system, as incorrect content may be served to users. Confidentiality and integrity are not directly compromised. The attack requires network access, has high complexity, and does not need privileges or user interaction.

Compliance Impact

This vulnerability primarily impacts data integrity and availability by allowing incorrect content to be served to users due to cache poisoning. While it does not directly expose or leak data, incorrect content delivery could lead to compliance violations if sensitive information is displayed to unauthorized users or if data processing errors occur. For GDPR, this could affect the accuracy of data processing (Article 5) and user rights. For HIPAA, it may impact the integrity of PHI if incorrect data is served.

Mitigation Strategies

Upgrade Next.js to version 15.5.27 or 16.3.8 or later to patch the vulnerability. If using self-hosted applications with Pages Router and SSG/ISR pages, verify the cache behavior and ensure no unauthorized content is being served.

Hi! I’m here to help you understand CVE-2026-94543. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70