Skip to content
VulniPulse
High8.3Red Hat Linux

High [CVE-2025-6032] Podman: podman missing tls verification

This high-severity Red Hat Linux advisory covers CVE-2025-6032 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.4 Extended Update Support.

CVE-2025-6032 Published Jun 24, 2025Updated by vendor Jun 24, 2025
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A flaw was found in Podman. The podman machine init command fails to verify the TLS certificate when downloading the VM images from an OCI registry.

This issue results in a Man In The Middle attack. To exploit this flaw, a user needs to download an image from an untrusted OCI registry, specifically, an OCI registry with an invalid TLS certificate.

Red Hat severity: Important — CVSS 8.3 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H). Weakness: CWE-295.

Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Enterprise Linux 9.4 Extended Update Support; Red Hat OpenShift Container Platform 4.16; Red Hat OpenShift Container Platform 4.17; Red Hat OpenShift Container Platform 4.18; Red Hat OpenShift Container Platform 4.19; Red Hat OpenShift Container Platform 4.20.

Red Hat fixing advisory: RHSA-2025:10549, RHSA-2025:10551, RHSA-2025:10550, RHSA-2025:10668, RHSA-2025:9766, RHSA-2025:11681, RHSA-2025:10295, RHSA-2025:11359, RHSA-2025:11677, RHSA-2025:9726, RHSA-2025:11363, RHSA-2025:9751, RHSA-2025:15397.

Affected products named by the advisory: Red Hat package: podman.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • podman-6:5.4.0-12.el10_0
  • container-tools:rhel8-8100020250625105344.afee755d
  • podman-5:5.4.0-12.el9_6
  • podman-4:4.9.4-18.el9_4.2
  • podman-4:4.9.4-14.rhaos4.16.el8
  • rhcos-416.94.202507222002-0
  • podman-5:5.2.2-8.rhaos4.17.el8
  • rhcos-417.94.202507132309-0
  • rhcos-418.94.202507221927-0
  • podman-5:5.2.2-9.rhaos4.18.el9
  • rhcos-4.19.9.6.202507152218-0
  • podman-5:5.4.0-6.rhaos4.19.el9
  • rhcos-4.20.9.6.202509251656-0
  • RHSA-2025:10549
  • RHSA-2025:10551
  • RHSA-2025:10550
  • RHSA-2025:10668
  • RHSA-2025:9766
  • RHSA-2025:11681
  • RHSA-2025:10295
  • RHSA-2025:11359
  • RHSA-2025:11677
  • RHSA-2025:9726
  • RHSA-2025:11363
  • RHSA-2025:9751
  • RHSA-2025:15397

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Download the VM image manually with another tool that verifies the TLS certificate and then pass the local image as a file path to podman, for example: # podman machine init --image <local-image-path>

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.