Vulnerability · CVE-2026-94484
Cache poisoning in Next.js SSG/ISR rendering leads to cross-user content substitution and persistent denial of service
Published Sep 30, 2026 · catalog updated Sep 30, 2026 · Cache poisoning in Next.js
Last checked Nov 5, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-94484. EPSS is 0.24%. Act only if a listed version of Cache poisoning in Next.js is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Cache poisoning in Next.js).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.24%
- Remediation
- Version ranges on file
- Affected products
- npm next
Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- npm next>= 15.0.0
- npm next>= 16.0.0
How to fix CVE-2026-94484
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
Seen in >= 15.0.0 · 1 other packages on the advisory
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-94484. EPSS is 0.24%. Act only if a listed version of Cache poisoning in Next.js is installed.
Which versions are affected?
Compare what you have installed with >= 15.0.0, >= 16.0.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 30, 2026 · Maintainer security tabs
Detected
Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.
Sources
- CVE.orgVulnerability recordCVE-2026-94484
Official CVE identifier
cve.org - Maintainer security tabsVendor advisoryGHSA-mcj8-r9mp-w47p
Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.
github.com
Freshness
Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 4, 2026
- Maintainer security tabsNov 2, 2026