Advisories
For your digest

static-eval: Sandbox Breakout / Arbitrary Code Execution in static-eval

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

static-eval (npm)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • static-eval (npm): every version, before 2.0.2

The fix

  • static-eval (npm) fixed in 2.0.2

    npm
    npm install static-eval@2.0.2
    pnpm
    pnpm add static-eval@2.0.2
    yarn
    yarn add static-eval@2.0.2
    bun
    bun add static-eval@2.0.2
    Check what is installed
    npm ls static-eval
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency static-eval to 2.0.2 or the nearest later release, to fix GHSA-x9hc-rw35-f44h. 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

  1. First published here, as "For your digest".