CVE-2024-46982
Cache Poisoning in next.js
Reported by github_m · Published September 17, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| jitsucom-jitsu | Wolfi | 2.8.2-r1 |
| next.js | vercel | 14.2.10, 13.5.7 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| vercel | next.js | >= 13.5.1, < 13.5.7, >= 14.0.0, < 14.2.10 |
| vercel | next.js | 13.5.1, 14.0.0 |
| wolfi | jitsucom-jitsu | 0 |
| chainguard | jitsucom-jitsu | 0 |
| vercel | next.js | 13.5.1, 14.0.0 |
| npm | next | 13.5.1, 14.0.0 |
Timeline
- Sep 17, 2024 CVE Published
- Sep 18, 2024 EPSS Score (30 in total, the first dated here)
- Sep 18, 2024 PoC Published (12 in total, the first dated here)
- Sep 18, 2024 CVE Updated
- Oct 5, 2024 Coalition ESS Score (29 in total, the first dated here)
- Dec 14, 2024 VulnCheck XDB Entry (4 in total, the first dated here)
- Jun 8, 2025 VulnCheck KEV Exploitation (2 in total, the first dated here)
- Jan 4, 2026 Security Advisory
- Aug 26, 2026 CrowdSec Sighting (2 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-46982
vulnetix vdb fixes CVE-2024-46982
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-46982/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://github.com/vercel/next.js/security/advisories/GHSA-gp8f-8m3g-qvj9 x_refsource_CONFIRM
- https://github.com/vercel/next.js/commit/7ed7f125e07ef0517a331009ed7e32691ba403d3 x_refsource_MISC
- https://github.com/vercel/next.js/commit/bd164d53af259c05f1ab434004bcfdd3837d7cda x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2024-46982 advisory
- https://github.com/advisories/GHSA-gp8f-8m3g-qvj9 advisory
- https://github.com/vercel/next.js url