CVSS 3.1
10.0 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCritical (10.0) in podman-container-tools podman. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/containers/podman/v4 5.8.8.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:Hgithub.com/containers/podman/v4 (Go): fixed in 5.8.8go.podman.io/podman/v6 (Go): fixed in 6.1.3github.com/containers/podman/v5 (Go): fixed in 5.8.8Explain CVE-2026-94603 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-94603?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-94603?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-94603 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| podman-container-tools podman | >= 4.4.0, < 5.8.8 |
| podman-container-tools podman | >= 6.0.0, < 6.1.3 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-2cvf-wqm6-wr9g | Go | github.com/containers/podman/v4 | >=4.4.0 <5.8.8 | 5.8.8 |
| GHSA-2cvf-wqm6-wr9g | Go | go.podman.io/podman/v6 | >=6.0.0 <6.1.3 | 6.1.3 |
| GHSA-2cvf-wqm6-wr9g | Go | github.com/containers/podman/v5 | >=4.4.0 <5.8.8 | 5.8.8 |
| GO-2026-6770 | Go | github.com/containers/podman | all versions | no fix published |
| GO-2026-6770 | Go | github.com/containers/podman/v2 | all versions | no fix published |
| GO-2026-6770 | Go | github.com/containers/podman/v3 | all versions | no fix published |
| GO-2026-6770 | Go | github.com/containers/podman/v4 | >=4.4.0 | no fix published |
| GO-2026-6770 | Go | github.com/containers/podman/v5 | <5.8.8 | 5.8.8 |
| GO-2026-6770 | Go | go.podman.io/podman/v6 | >=6.0.0 <6.1.3 | 6.1.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | podman | no fix listed | DEBIAN-CVE-2026-94603 |
| Debian | 14 | podman | 5.8.6+ds1-3 | DEBIAN-CVE-2026-94603 |
| Ubuntu | 26.04:LTS, 26.10 | podman | no fix listed | UBUNTU-CVE-2026-94603 |
| Red Hat | enterprise_linux:10.2 | podman, podman-tests, podman-docker and 5 more | 7:5.8.2-10.el10_2 | RHSA-2026:88202 |
| Red Hat | hummingbird:1 | podman, podmansh, podman-docker and 2 more | 0:6.1.3-1.hum1 | RHSA-2026:74861 |
| Red Hat | hummingbird:1 | podman, podmansh, podman-docker and 2 more | 5:6.1.2-1.1.hum1 | RHSA-2026:74178 |
| Red Hat | rhel_eus:9.8::appstream | podman, podman-tests, podman-docker and 7 more | 6:5.8.2-10.el9_8 | RHSA-2026:99093 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | govulncheck-vulndb | 0.0.20261105T234957-160000.1.1 | SUSE-SU-2026:24730-1 |
| openSUSE | Tumbleweed | podman | 6.1.4-1.1 | openSUSE-SU-2026:12370-1 |
| AlmaLinux | 10 | podman-docker | 7:5.8.2-10.el10_2.alma.1 | ALSA-2026:88202 |
| Alpine | v3.24 | podman | 5.8.8-r0 | ALPINE-CVE-2026-94603 |
| Azure Linux | 3 | libcontainers-common | no fix listed | AZL-108390 |
| Azure Linux | 3 | podman | no fix listed | AZL-108315 |
| Alpaquita | stream | podman | 6.1.3-r0 | BELL-CVE-2026-94603 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.
Red Hat rates this Important.
This vulnerability is rated as having an Important severity impact for Red Hat environments because running a malicious image can completely circumvent expected confinement boundaries and grant unexpected privileges to a container, compromising host integrity. Under default configurations, container execution relies on enforced sandboxing limits and security flags supplied by the operator. However, if an image embeds specific checkpoint metadata, the runtime automatically prioritizes the checkpoint configuration over explicit command-line restrictions, silently omitting requested security controls. Exploitation requires an operator or automated workflow to launch an untrusted image; environments that execute only vetted container workloads from trusted registries remain at reduced operational risk.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | podman-7:5.8.2-10.el10_2 | Fixed 2026-10-22 | RHSA-2026:88202 |
| Red Hat Enterprise Linux 9.8 Extended Update Support | podman-6:5.8.2-10.el9_8 | Fixed 2026-11-11 | RHSA-2026:99093 |
| Red Hat Hardened Images | podman-main-6.1.2-1.1.hum1 | Fixed 2026-10-01 | RHSA-2026:74178 |
| Red Hat Hardened Images | podman-main-6.1.3-1.hum1 | Fixed 2026-10-02 | RHSA-2026:74861 |
| Red Hat Quay 3.10 | quay/quay-builder-rhel8:1793136434 | Fixed 2026-11-11 | RHSA-2026:99025 |
| Red Hat Quay 3.12 | quay/quay-rhel8:1791314514 | Fixed 2026-10-08 | RHSA-2026:79546 |
| Red Hat Quay 3.14 | quay/quay-builder-rhel8:1793137593 | Fixed 2026-11-11 | RHSA-2026:99024 |
| Red Hat Quay 3.15 | quay/quay-builder-rhel8:1793136553 | Fixed 2026-11-11 | RHSA-2026:99023 |
| Red Hat Quay 3.16 | quay/quay-builder-rhel9:1793117209 | Fixed 2026-11-11 | RHSA-2026:99022 |
| Red Hat Quay 3.18 | quay/quay-builder-rhel9:1793115574 | Fixed 2026-11-11 | RHSA-2026:99019 |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/eda-controller-rhel8 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/eda-controller-rhel8 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-26/eda-controller-rhel9 | Affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-27/eda-controller-rhel9 | Affected | |
| Red Hat Build of Podman Desktop | rh-podman-desktop | Affected | |
| Red Hat Enterprise Linux 8 | container-tools:rhel8/podman | Affected | |
| Red Hat Enterprise Linux 9 | podman | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Container Platform 4 | podman | Affected | |
| 5 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-94603.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).