For your digest
next: Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
It touches something Phylax follows. No evidence of use yet.
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.0.0, before 15.0.8
- next (npm): from 15.1.1-canary.0, before 15.1.12
- next (npm): from 15.2.0-canary.0, before 15.2.9
- next (npm): from 15.3.0-canary.0, before 15.3.9
- next (npm): from 15.4.0-canary.0, before 15.4.11
- next (npm): from 15.5.1-canary.0, before 15.5.10
- next (npm): from 15.6.0-canary.0, before 15.6.0-canary.61
- next (npm): from 16.0.0-beta.0, before 16.0.11
- next (npm): from 16.1.0-canary.0, before 16.1.5
The fix
next (npm) fixed in 15.0.8
npmnpm install next@15.0.8pnpmpnpm add next@15.0.8yarnyarn add next@15.0.8bunbun add next@15.0.8Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.0.8 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 15.1.12
npmnpm install next@15.1.12pnpmpnpm add next@15.1.12yarnyarn add next@15.1.12bunbun add next@15.1.12Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.1.12 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 15.2.9
npmnpm install next@15.2.9pnpmpnpm add next@15.2.9yarnyarn add next@15.2.9bunbun add next@15.2.9Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.2.9 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 15.3.9
npmnpm install next@15.3.9pnpmpnpm add next@15.3.9yarnyarn add next@15.3.9bunbun add next@15.3.9Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.3.9 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 15.4.11
npmnpm install next@15.4.11pnpmpnpm add next@15.4.11yarnyarn add next@15.4.11bunbun add next@15.4.11Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.4.11 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 15.5.10
npmnpm install next@15.5.10pnpmpnpm add next@15.5.10yarnyarn add next@15.5.10bunbun add next@15.5.10Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.5.10 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 15.6.0-canary.61
npmnpm install next@15.6.0-canary.61pnpmpnpm add next@15.6.0-canary.61yarnyarn add next@15.6.0-canary.61bunbun add next@15.6.0-canary.61Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 15.6.0-canary.61 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 16.0.11
npmnpm install next@16.0.11pnpmpnpm add next@16.0.11yarnyarn add next@16.0.11bunbun add next@16.0.11Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 16.0.11 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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 16.1.5
npmnpm install next@16.1.5pnpmpnpm add next@16.1.5yarnyarn add next@16.1.5bunbun add next@16.1.5Check what is installednpm ls nextPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next to 16.1.5 or the nearest later release, to fix GHSA-h25m-26qc-wcjf. 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
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".