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