CVSS 4.0
4.0 mediumCVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:UMedium (4.0) in podman project podman. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/containers/podman/v5 5.8.2.
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:UCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:Hgithub.com/containers/podman/v5 (Go): fixed in 5.8.2Explain CVE-2026-33414 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33414?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33414?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-33414 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 NVD's CPE matches.
| Product | Affected |
|---|---|
| podman_project:podman | from 4.8.0 before 5.8.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-hc8w-h2mf-hp59 | Go | github.com/containers/podman/v4 | >=4.8.0 <=4.9.5 | no fix published |
| GHSA-hc8w-h2mf-hp59 | Go | github.com/containers/podman/v5 | <5.8.2 | 5.8.2 |
| GO-2026-5421 | Go | github.com/containers/podman | all versions | no fix published |
| GO-2026-5421 | Go | github.com/containers/podman/v2 | all versions | no fix published |
| GO-2026-5421 | Go | github.com/containers/podman/v3 | all versions | no fix published |
| GO-2026-5421 | Go | github.com/containers/podman/v4 | >=4.8.0 | no fix published |
| GO-2026-5421 | Go | github.com/containers/podman/v5 | <5.8.2 | 5.8.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | podman | no fix listed | DEBIAN-CVE-2026-33414 |
| Debian | 14 | podman | 5.8.2+ds1-1 | DEBIAN-CVE-2026-33414 |
| Ubuntu | 25.10, 26.04:LTS, 26.10 | podman | no fix listed | UBUNTU-CVE-2026-33414 |
| Red Hat | hummingbird:1 | podman, podmansh, podman-tests and 3 more | 0:5.8.2-1.hum1 | RHSA-2026:8211 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Tumbleweed | podman | 5.8.2-1.1 | openSUSE-SU-2026:10706-1 |
| Azure Linux | 3 | podman | no fix listed | AZL-82985 |
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; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.
Red Hat rates this Important.
This flaw in Podman's HyperV backend does not affect Red Hat products. The vulnerable code path is exclusive to Windows installations, and the HyperV backend is not utilized on Red Hat Enterprise Linux or OpenShift Container Platform.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | podman-main-5.8.2-1.hum1 | Fixed 2026-04-14 | RHSA-2026:8211 |
| Red Hat Enterprise Linux 10 | podman | Not affected | |
| Red Hat Enterprise Linux 8 | container-tools:rhel8/podman | Not affected | |
| Red Hat Enterprise Linux 9 | podman | Not affected | |
| Red Hat OpenShift Container Platform 4 | podman | Not affected | |
| Red Hat OpenShift Container Platform 4 | rhcos | Not affected |
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-33414.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.