Menu

Podman Checkpoint CVE: How a Sandbox Bypass Works
πŸ“°

Podman Checkpoint CVE: How a Sandbox Bypass Works

DEV Community: dockerΒ·Amaresh PelletiΒ·15 days ago
#EPvMLOo2
#devtodocker#devto#dev#podman#checkpoint
Reading 0:00
15s threshold

Originally published on DevToolHub .

If you run Podman in production, a container image can now disable the sandbox restrictions you explicitly asked for, just by carrying one annotation. CVE-2026-94603 is a podman checkpoint handling bug that tricks podman run into treating an ordinary image as a restored checkpoint, which silently overrides flags like --cap-drop=ALL . Here's exactly how the bypass works, who it actually reaches, and what you need to patch.

What Happened: A Crafted Image Can Turn Off Your Sandbox

Podman's run command is supposed to enforce whatever sandboxing flags you pass it. Run it with --cap-drop=ALL and you expect zero Linux capabilities inside that container, no exceptions.

CVE-2026-94603 breaks that guarantee. A container image carrying a specific annotation makes Podman treat your run command as if it were restoring a checkpoint instead of starting a fresh container. Checkpoint restores are allowed to bring their own capability set with them, so your flags get silently dropped.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.