Skip to content

Get notified

Get an email when a new major security incident drops. No spam, unsubscribe any time.

Only used for pwn.watch incident emails. Protected by Cloudflare Turnstile.

Become a sponsor

One slot: pwn.watch, gifs.so, flavors.design, kitze.io, every kitze repo, and an X shout-out.

Secure checkout on Polar. Right after paying you set up your ad on kitze.io.

Sandboxes

Security incidents tagged Sandboxes. Newest first.

1 Sandboxes incident in the last 12 months

Critical 4 · High 3 · Med 2 · Low 1 · Update ½LessMore
Incidents
1
Live
1
Patched
1
Days without an incident
9
Longest quiet run: 7 days (Oct 27–Nov 2)

Brought to you byTinkerer Club

The private club for people who own their servers, run their own AI, and pay $0/month for software.

  • Patched

    Docker Sandboxes sandbox escape via poisoned Git config (CVE-2026-121614)

    CVE-2026-121614 affects Docker Sandboxes 0.31.0 before 0.50.0. Host-side Git commands did not neutralize repository-controlled Git configuration. An attacker who can modify a host repository's Git config—for example through a direct-mode sandbox with the repo mounted read-write—can set core.fsmonitor or another setting that invokes an external program. A later clone-mode fetch, or from 0.39.0 an sbx kit push, can run that program on the host with the user's privileges, outside the microVM. Clone-mode's read-only host mount alone cannot poison the config. Fixed in Docker Sandboxes 0.50.0 (released Oct 26 2026; CVE published ~Nov 3). Vendor CVSS 4.0 is 7.1 (High). Upgrade to 0.50.0+; avoid read-write mounts of untrusted repos until patched.

    Docker Sandboxes (sbx)Since Oct 26, 2026