For your digest
safer-eval: Sandbox Breakout / Arbitrary Code Execution in safer-eval
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
safer-eval (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- safer-eval (npm): every version, before 1.3.2
The fix
safer-eval (npm) fixed in 1.3.2
npmnpm install safer-eval@1.3.2pnpmpnpm add safer-eval@1.3.2yarnyarn add safer-eval@1.3.2bunbun add safer-eval@1.3.2Check what is installednpm ls safer-evalPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency safer-eval to 1.3.2 or the nearest later release, to fix CVE-2019-10760. 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".