Digest · Monday

Security digest: August 17, 2026

1 editorial brief, 1 known exploited (cisa kev) addition and 7 critical advisories.

All digests · RSS · Markdown

Take stock

  • Check exposure: vm2: 22 Critical Sandbox Escapes, Fixed in 3.12.2. Apps that use vm2 to run user-, tenant- or model-supplied JavaScript (plugin systems, rule and template engines, workflow and low-code tools, online code runners, AI agent code tools), directly or through a dependency.
  • Do you run any of these? Ray-Project Ray. They are being exploited in the wild (CISA KEV). Patch or mitigate if you do; CISA’s federal deadline is 2026-08-20.
  • npm: 3 critical advisories (vm2). Check with npm audit (or: npm ls <package>).
  • Go: 2 critical advisories (github.com/QuantumNous/new-api). Check with govulncheck ./....
  • PyPI: 1 critical advisory (mlflow). Check with pip-audit (or: pip show <package>).
  • GitHub Actions: 1 critical advisory (wktk/conflibot). Check with grep -rn 'uses: <owner>/<action>' .github/workflows.
  • None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.

Editorial briefs

Check exposure

· Vulnerability · CVE-2026-47683, CVE-2026-47686

vm2: 22 Critical Sandbox Escapes, Fixed in 3.12.2

If anything outside your trust boundary can get code into vm2, upgrade to 3.12.2 today and plan to move that code out of process; if vm2 only runs your own code, upgrade on a normal cycle.

Must act: Apps that use vm2 to run user-, tenant- or model-supplied JavaScript (plugin systems, rule and template engines, workflow and low-code tools, online code runners, AI agent code tools), directly or through a dependency.

Can relax: Projects where vm2 is a transitive dependency that never evaluates attacker-influenced code; patch it, but no escape is reachable without control of the sandboxed script.

  1. Find every copy: run npm ls vm2 --all (or pnpm why vm2 / yarn why vm2) in each service and image.
  2. Upgrade to vm2 3.12.2, forcing transitive copies with an npm overrides (or pnpm/yarn resolutions) entry, then rebuild and redeploy.
  3. If the sandbox runs code from outside your trust boundary, move it to stronger isolation: a separate low-privilege process or Worker, a container, gVisor or Firecracker, as the vm2 README recommends.

Read the brief →

Known exploited (CISA KEV) 1

Added to CISA’s catalog on this day: confirmed exploitation in the wild. Due date = CISA’s deadline for US federal agencies.

CVEProduct and flawCISA due
CVE-2025-62593Ray-Project Ray
Ray-Project Ray Code Injection Vulnerability
2026-08-20

Critical advisories by ecosystem 7

GitHub-reviewed advisories rated critical, published this day (Pacific time).

npm 3

Check: npm audit (or: npm ls <package>)

Go 2

Check: govulncheck ./...

GitHub Actions 1

Check: grep -rn 'uses: <owner>/<action>' .github/workflows

PyPI 1

Check: pip-audit (or: pip show <package>)