All vulnerabilities

Servers and applications

CVE-2026-94603

The `podman run` command can be instructed to disable almost all sandboxing - including user-requested sandboxing - by image annotation

Severity
Critical 10.0
Published
29 Sept 2026
Last changed
13 Oct 2026
Added to UpHeron
3 Nov 2026
Fixed in
5.8.8, 6.1.3
Exploit chance
0.7% in the next 30 daysHigher than 52% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Protection mechanism failure (CWE-693)
Attack
Over the network · No login needed · No user action needed
Attacker can
Read data · Change data · Take it down
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Also known as
GHSA-2cvf-wqm6-wr9g
Sources
CVE Program, Project advisories (GitHub)

Description

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 podman run detects a checkpoint, it will silently ignore all user input regarding how the container should be created - for example, podman run --cap-drop=ALL on an image that is determined to be a checkpoint will ignore --cap-drop=all 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, io.podman.annotations.checkpoint.runtime.name. If this annotation is set, the image is treated as a checkpoint.

From podman-container-tools/podman's security advisory. Shortened; the full text is there.

Workarounds

Images being pulled should be scanned for the io.podman.annotations.checkpoint.runtime.name 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.

Workarounds as given by podman-container-tools/podman's security advisory.

Affected software

SoftwareAffected versions
PodmanServers and applications · cna:podman-container-tools|podman
  • From 4.4.0 before 5.8.8
  • From 6.0.0 before 6.1.3
PodmanServers and applications · github:podman-container-tools/podman
  • From 4.4.0 before 5.8.8

About Podman

daemonless OCI-compliant container runtime

From Wikidata, CC0 1.0.
Developers who used it in the past year
11.1%Stack Overflow Developer Survey 2025, 2025
GitHub stars
33,281GitHub, 15 Nov 2026
Forks
3,458GitHub, 15 Nov 2026
Latest release
v6.2.0GitHub, 15 Nov 2026
Released
10 Nov 2026GitHub
Developer
Matt HeonWikidata
License
Apache Software License 2.0Wikidata
Written in
GoWikidata
First published on GitHub
1 Nov 2017GitHub

Release lines

ReleaseLatestSecurity fixes
6.16.1.4Yes
6.06.0.2Ended 12 Aug 2026
5.85.8.10Ended 26 Sept 2026
5.75.7.1Ended 12 Feb 2026
5.65.6.2Ended 11 Nov 2025
5.55.5.2Ended 15 Aug 2025

From endoflife.date.

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-94603
  • GitHub Advisory Database https://github.com/advisories/GHSA-2cvf-wqm6-wr9g
  • github.com https://github.com/podman-container-tools/podman/security/advisories/GHSA-2cvf-wqm6-wr9g