For your digest
next-intl: next-intl has prototype pollution with `experimental.messages.precompile` via attacker-controlled translation catalog keys
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
next-intl (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- next-intl (npm): every version, before 4.9.2
The fix
next-intl (npm) fixed in 4.9.2
npmnpm install next-intl@4.9.2pnpmpnpm add next-intl@4.9.2yarnyarn add next-intl@4.9.2bunbun add next-intl@4.9.2Check what is installednpm ls next-intlPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next-intl to 4.9.2 or the nearest later release, to fix GHSA-4c35-wcg5-mm9h. 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".