CVE-2024-46982: Cache Poisoning in next.js

Severity: high (CVSS 7.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 59.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-09-17 · updated 2026-06-17
Weakness: CWE-639

Description

Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a `Cache-Control: s-maxage=1, stale-while-revalidate` header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g. `pages/dashboard.tsx` not `pages/blog/[slug].tsx`. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.

Affected products

Next.js: from 13.5.1 before 13.5.7; from 14.0.0 before 14.2.10 — fixed in 13.5.7, 14.2.10

How to fix

Upgrade to a fixed version: Next.js 13.5.7, 14.2.10. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-46982 or the next vulnerability affects your stack