cve.bz

CVE-2026-121885 Podman: untrusted image labels allow auto-update to restart arbitrary systemd units

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in red hat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in Podman. An attacker can trigger a Denial of Service (DoS) by supplying a container image containing crafted metadata labels. Podman's auto-update mechanism improperly trusts these image labels to determine which system services to restart. If a user runs the malicious container and auto-update processes it, arbitrary system services are restarted with the user's privileges, potentially allowing an attacker to shut down the host system when Podman runs with administrative privileges.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-807 Reliance on Untrusted Inputs in a Security Decision
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2026-121885

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-121885](https://cve.bz/cve/badge/CVE-2026-121885.svg)](https://cve.bz/cve/CVE-2026-121885)

HTML:

<a href="https://cve.bz/cve/CVE-2026-121885"><img src="https://cve.bz/cve/badge/CVE-2026-121885.svg" alt="CVE-2026-121885"></a>

Affected

  • red hat:red hat enterprise linux 10
  • red hat:red hat enterprise linux 8
  • red hat:red hat enterprise linux 9
  • red hat:red hat hardened images
  • red hat:red hat openshift container platform 4

Versions

From the CNA's record in the CVE List.

ProductAffected
podmanfrom 1.8.2 before 5.8.10
podmanfrom 6.0.0 before 6.2.0

Fixed in

ProductFixed in
Red Hat Hardened Images6.1.4-1.4.hum1

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.04:LTS, 26.10podmanno fix listedUBUNTU-CVE-2026-121885
Red Hathummingbird:1podman, podmansh, podman-docker and 2 more5:6.1.4-1.4.hum1RHSA-2026:98992
Azure Linux3libcontainers-commonno fix listedAZL-113552
Azure Linux3podmanno fix listedAZL-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

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10podmanFix deferred
Red Hat Enterprise Linux 8container-tools:rhel8/podmanFix deferred
Red Hat Enterprise Linux 9podmanFix deferred
Red Hat Hardened ImagespodmanAffected
Red Hat OpenShift Container Platform 4podmanFix 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.

References

Check your stackJSON