CVE-2026-94543

Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications

Published Oct 2, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Next.js, a React framework for full‑stack web applications, has a cache‑poisoning flaw in versions 15.0.0 through 15.5.26 and 16.0.0 through 16.3.7. The bug allows a request to the response cache to be keyed without sufficient binding to the source route, meaning an attacker can craft a request that replaces a page’s cache entry with content from a different route. The poisoned cache entry can then be served to every visitor until the entry is revalidated or purged, effectively compromising the integrity of the content delivered by the application and potentially misleading users or exposing sensitive information.

Affected Systems

Self‑hosted Next.js deployments that use the Pages Router for statically generated or Incremental Static Regeneration pages and run any version from 15.0.0 through 15.5.26 or from 16.0.0 through 16.3.7 are affected; applications hosted on Vercel remain secure. The issue is fixed in Next.js 15.5.27 and 16.3.8, and all later releases are not vulnerable.

Risk and Exploitability

The CVSS base score of 6.3 indicates moderate severity; the EPSS score is not available, so exploitation probability is unknown. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the attack vector is a crafted HTTP request to a cached route; no authentication is required. Once the cache entry is poisoned, the incorrect content is served to all users of the compromised page until the cache is purged or revalidated, giving the attacker a broad and persistent impact.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Next.js application to at least version 15.5.27 for 15.x releases or 16.3.8 for 16.x releases to apply the bug fix.
  • Purge or revalidate all statically generated and Incremental Static Regeneration pages, and clear any CDN or edge caches that may still hold cached entries for the affected routes.
  • Review any custom cache‑key logic or CDN configuration to ensure that cache keys are tightly bound to the originating route, preventing future key mismatches.

Generated by OpenCVE AI on October 3, 2026 at 01:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-4jqv-mc3x-m676 Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
Metrics cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L'}

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Type Values Removed Values Added
Weaknesses CWE-694
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Vercel
Vercel next.js
Vendors & Products Vercel
Vercel next.js
Type Values Removed Values Added
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.
Title Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications
Weaknesses CWE-524
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-524

    Use of Cache Containing Sensitive Information

  • CWE-694

    Use of Multiple Resources with Duplicate Identifier

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 6, 2026, 4:31 PM
Reserved
Sep 21, 2026, 7:21 PM
Status
Analyzed
Published
Oct 2, 2026, 4:16 PM
Modified
Oct 6, 2026, 5:17 PM
Severity
Moderate
Public date
Oct 2, 2026, 3:16 PM