For your digest
assign-deep: Prototype Pollution in assign-deep
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
assign-deep (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- assign-deep (npm): every version, before 0.4.7
The fix
assign-deep (npm) fixed in 0.4.7
npmnpm install assign-deep@0.4.7pnpmpnpm add assign-deep@0.4.7yarnyarn add assign-deep@0.4.7bunbun add assign-deep@0.4.7Check what is installednpm ls assign-deepPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency assign-deep to 0.4.7 or the nearest later release, to fix CVE-2018-3720. 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".