CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HMedium (6.5) in red hat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExplain CVE-2026-121885 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121885?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121885?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-121885 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 | from 1.8.2 before 5.8.10 |
| podman | from 6.0.0 before 6.2.0 |
| Product | Fixed in |
|---|---|
| Red Hat Hardened Images | 6.1.4-1.4.hum1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | 26.04:LTS, 26.10 | podman | no fix listed | UBUNTU-CVE-2026-121885 |
| Red Hat | hummingbird:1 | podman, podmansh, podman-docker and 2 more | 5:6.1.4-1.4.hum1 | RHSA-2026:98992 |
| Azure Linux | 3 | libcontainers-common | no fix listed | AZL-113552 |
| Azure Linux | 3 | podman | no fix listed | AZL-113342 |
From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Red Hat.
Red Hat rates this Moderate.
This vulnerability is rated as Moderate impact because triggering it requires user interaction to pull and run an untrusted container image, and its blast radius is restricted to a denial of service via systemd unit restarts rather than arbitrary code execution. In default Red Hat Enterprise Linux configurations, the podman-auto-update timer is not enabled, meaning automated container processing does not occur unless explicitly configured by an administrator. Furthermore, in standard rootless container environments, systemd control is limited to the user's personal session, preventing unauthorized interference with core host services.
Do not use podman auto-update on untrusted containers or images. Before running an image, inspect its labels with podman image inspect --format '.Config.Labels' and verify that the io.containers.autoupdate and PODMAN_SYSTEMD_UNIT labels are not set. For existing containers, inspect their labels and ensure that auto-update labels are configured correctly and only present on containers intended to use auto-update.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | podman | Fix deferred | |
| Red Hat Enterprise Linux 8 | container-tools:rhel8/podman | Fix deferred | |
| Red Hat Enterprise Linux 9 | podman | Fix deferred | |
| Red Hat Hardened Images | podman | Affected | |
| Red Hat OpenShift Container Platform 4 | podman | Fix deferred |
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-121885.