CVE-2024-46982

highpriority · track · 31EPSS 0.592 · 99 %ileexploit · PoCEURUUS

grimoire priorityP1 · Urgent

Exploitable?

Public exploit

5 exploits · PoC

Likely / severe?

59.2% (99th) EPSS

CVSS 7.5 · high

Is it mine?

8 products

Check your exposure

Who says so?

5 sources

cnnvd · enisa_euvd · fstec_bdu · nvd

EPSS · scored 2026-10-26

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.

cvss

Technical severity, 0–10. One row per scoring source.

7.5

010

base score 0–10 · higher = more severe · hover a vector to decode

v3.17.5highAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · FSTEC (BDU) RU

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · ENISA EU

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · security-advisories@github.comexploitability 3.9 · impact 3.6

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · OSV

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:Hsecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: yes · Technical Impact: partialcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-349USCWE-639USCWE-639USCWE-639US

exploits (5)

Public proof-of-concept and weaponised exploit code.

CodePontiff/next_js_poisoning The CVE-2024-46982 is cache poisoning of next_js some site have API to load their imagePoC · poc_in_github
Lercas/CVE-2024-46982POC CVE-2024-46982PoC · poc_in_github
hidesec/CVE-2025-32421Comprehensive demonstration of CVE-2025-32421 Eclipse technique - a sophisticated race condition attack against Next.js 15.0.4 that bypasses the original CVE-2024-46982 patch.PoC · poc_in_github
melmathari/CVE-2024-46982-NUCLEImelmathari/CVE-2024-46982-NUCLEIPoC · poc_in_github
samuel871211/CVE-2024-46982-ReproductionReproduction of CVE-2024-46982PoC · poc_in_github

affected products (8)

Products and version ranges known to be affected.

vercel next.js13.5.1, → 13.5.7enisa_euvdEU
vercel next.js14.0.0, → 14.2.10enisa_euvdEU
vercel next.js≤ 14.2.10fstec_bduRU
vercel next.js≤ 13.5.7fstec_bduRU
vercel next.js13.5.1 → 13.5.7nvdUScpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:*
vercel next.js14.0.0 → 14.2.10nvdUScpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:*
npm next13.5.1 → 13.5.7osvUSpkg:npm/next
npm next14.0.0 → 14.2.10osvUSpkg:npm/next

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-gp8f-8m3g-qvj9Next.js Cache Poisoning2024-09-17ghsa · osvUS
### Impact 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: - Next.js between 13.5.1 and 14.2.9 - Using pages router - Using non-dynamic server-side rendered routes e.g. `pages/dashboard.tsx` not `pages/blog/[slug].tsx` The below configurations are unaffected: - Deployments using only app router - Deployments on [Vercel](https://vercel.com/) are not affected ### Patches 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. ### Workarounds There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version. #### Credits - Allam Rachid (zhero_) - Henry Chen

also known as (4)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd fstec_bdu nvd osv NVD CVE.org MITRE

published 2024-09-17modified 2026-06-17

references (11)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan