Skip to main content
CVE-2026-121885VulnerabilityPublished Updated

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Affects Red HatSource GCVE Database

0
Compare
Authoritative record:CVE-2026-121885· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade Red Hat podman to 6.2.0 or 5.8.10 when convenient.

Data as of 13 Nov 2026, 14:32 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.16.5
Patch
Available – fixed in 6.2.0, 5.8.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade podman to 6.2.0 or 5.8.10.

Affected software

ProductAffectedFixed in
podmanAffected
  • >=6.0.0 <6.2.0
Fixed in
  • 6.2.0
podmanAffected
  • >=1.8.2 <5.8.10
Fixed in
  • 5.8.10
GitHubpodmanpkg:github/podmanOther threatsAffected
  • >=1.8.2 <5.8.10
  • >=6.0.0 <6.2.0
Fixed in
  • 5.8.10
  • 6.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in the updated podman packages version 6.1.4-1.4.hum1 provided by Red Hat. Users should apply this update to remediate the vulnerability. Additionally, do not use podman auto-update on untrusted containers or images. Inspect container image labels before running them using 'podman image inspect --format '.Config.Labels'' to verify that 'io.containers.autoupdate' and 'PODMAN_SYSTEMD_UNIT' labels are not set. For existing containers, inspect and ensure auto-update labels are configured only on intended containers. In default configurations where podman-auto-update timer is disabled, no automated processing occurs unless explicitly enabled by an administrator.

Description

A vulnerability in Podman allows an attacker to cause a denial of service by supplying a container image with crafted metadata labels. Podman's auto-update mechanism improperly trusts these labels to decide which system services to restart. If exploited, arbitrary systemd services may be restarted with the user's privileges, potentially shutting down the host system when Podman runs with administrative rights. The vulnerability requires user interaction to pull and run a malicious container image. In default Red Hat Enterprise Linux configurations, the auto-update timer is disabled, limiting exposure. Rootless container environments further restrict the impact by limiting systemd control to the user's session.

References

Community reviews

Loading reviews…