This weekExploitable · Confirmed
next: Next.js Cache Poisoning
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
next (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- next (npm): from 13.5.1, before 13.5.7
- next (npm): from 14.0.0, before 14.2.10
The fix
next (npm) fixed in 13.5.7
npmnpm install next@13.5.7pnpmpnpm add next@13.5.7yarnyarn add next@13.5.7bunbun add next@13.5.7Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 13.5.7 or the nearest later release, to fix CVE-2024-46982. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.next (npm) fixed in 14.2.10
npmnpm install next@14.2.10pnpmpnpm add next@14.2.10yarnyarn add next@14.2.10bunbun add next@14.2.10Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 14.2.10 or the nearest later release, to fix CVE-2024-46982. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
EPSS puts the chance of exploitation in the next 30 days at 59%.
FIRST EPSSStated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)