ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-94603

Podman: The command can be instructed to disable almost all sandboxing by image annotation

Published Oct 15, 2026 · catalog updated Oct 15, 2026 · Podman: The command can

Check if you run it

No confirmed exploitation is on record for CVE-2026-94603. EPSS is 0.92%. Act only if a listed version of Podman: The command can is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Podman: The command can).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical10.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.92%
Remediation
Version ranges on file
Affected products
go github.com/containers/podman · go go.podman.io/podman/v6 · golang github.com · golang go.podman.io

### Impact Podman v4.4.0 added a feature where container checkpoints (from the command) could be distributed via OCI registry, and pulled from that registry and run via the command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, on an image that is determined to be a checkpoint will ignore and use the set of capabilities specified by the checkpoint image instead, which could include all capabilities. Podman identifies checkpoint images by looking for an annotation, . If this annotation is set, the image is treated as a checkpoint. Conflating container images and checkpoints in allows inherently insecure behavior as the image can now control how it is executed. The Podman Maintainers have determined that the safest course of action is to remove this functionality. ### Patch The commit introducing this functionality was reverted. 3721ff82ffb44a4ceeaecc5abd3808e924a6b669 c74b1d37b3fb834b0de43e176565d9d8c254b627 fa6cef22c2baf3987b581c673bb416ef0585daf7 (main) ea9243e04d1db3886dc3a51ee3300ffb547cfc02 450c64426dbcff1097d3c7911d791101e3d16f4c 2d05a7c61f022d4f24980ea6d307fa53da2b8692 (v6.1) 7728ba0a90094408ad9078e36c3622a651d49616 24706290d5c974f078d8ca284026802515f28e92 29c8c6e50607df7a7d735ace09ff0ea099c0b3e0 (v5.8) ### Workarounds Images being pulled should be scanned for the annotation, and rejected if it is present. Podman does not presently have the ability to perform this scanning and rejection automatically. Also not that rootless containers are not affected as they do not support checkpoint/restore at all currently. ### Credits This vulnerability was discovered by ADA Logics Ltd using Anthropic's Claude models.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • go github.com/containers/podman>= 4.4.0, < 5.8.8
  • go go.podman.io/podman/v6>= 6.0.0, < 6.1.3
  • golang github.comversion unspecified
  • golang go.podman.ioversion unspecified

How to fix CVE-2026-94603

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-94603. EPSS is 0.92%. Act only if a listed version of Podman: The command can is installed.

Which versions are affected?

Compare what you have installed with >= 4.4.0, < 5.8.8, >= 6.0.0, < 6.1.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-693: Protection Mechanism Failure. EPSS 0.92%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 15, 2026 · GitHub Advisory Database

    Detected

    ### Impact Podman v4.4.0 added a feature where container checkpoints (from the command) could be distributed via OCI registry, and pulled from that registry and run via the command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When detects a checkpoint, it wi

  2. Oct 15, 2026 · GitHub Advisory Database

    Updated

    ### Impact Podman v4.4.0 added a feature where container checkpoints (from the command) could be distributed via OCI registry, and pulled from that registry and run via the command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When detects a checkpoint, it wi

Sources

  • CVE.orgVulnerability recordCVE-2026-94603

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-94603

    30-day exploitation probability 0.9%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-2cvf-wqm6-wr9g

    Podman: The command can be instructed to disable almost all sandboxing by image annotation

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-94603

    Podman v4.4.0 added a feature where container checkpoints (from the podman container checkpoint command) could be distributed via OCI registry, and pulled from that registry and run via the podman run command. This allowed easy transfer of checkpoints between systems. However, checkpoints allow complete control of how the container is created - including full control of the container sandbox. When

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.