CVE-2025-6032: Podman TLS Verification Vulnerability

CVE-2025-6032 Overview

A security flaw was discovered in Podman where the podman machine init command fails to properly verify TLS certificates when downloading VM images from an OCI registry. This improper certificate validation vulnerability (CWE-295) enables Man-in-the-Middle (MITM) attacks, allowing attackers positioned on the network path to intercept and potentially modify VM image downloads without detection.

Critical Impact

Attackers can intercept VM image downloads during Podman machine initialization, potentially serving malicious VM images that could lead to full system compromise when the container runtime environment is initialized.

Affected Products

• Podman (containers/podman)
• Red Hat Enterprise Linux distributions with Podman packages
• OpenShift and related container platform deployments

Discovery Timeline

• June 24, 2025 - CVE-2025-6032 published to NVD
• November 29, 2025 - Last updated in NVD database

Technical Details for CVE-2025-6032

Vulnerability Analysis

The vulnerability exists in Podman's OCI artifact pulling mechanism used during machine initialization. The core issue stems from a logic error in how the TLS verification option was being applied. The code was incorrectly negating the TLSVerify boolean value when setting the DockerInsecureSkipTLSVerify option, which resulted in the opposite behavior than intended—when users expected TLS verification to be enabled, it was actually being disabled.

This improper certificate validation allows an attacker with network-level access (such as through ARP spoofing, DNS hijacking, or rogue access points) to intercept HTTPS connections to OCI registries and serve malicious VM images. The attack requires user interaction (initiating the podman machine init command) and high attack complexity due to the need for network positioning.

Root Cause

The root cause lies in the pkg/machine/ocipull/ociartifact.go file where the DockerInsecureSkipTLSVerify configuration was being set incorrectly. The original code used:

DockerInsecureSkipTLSVerify: types.NewOptionalBool(!o.pullOptions.TLSVerify)

This logic inverted the user's intention—when TLSVerify was true (meaning "verify TLS"), the negation made InsecureSkipTLSVerify become false, but the type conversion through NewOptionalBool introduced unexpected behavior. The fix changes the option to use a dedicated SkipTLSVerify field with proper types.OptionalBool type handling.

Source: GitHub Podman Commit Update

Attack Vector

The attack is network-based and requires the attacker to position themselves between the victim and the OCI registry. When a user executes podman machine init, the command downloads VM images from a registry. Due to the certificate validation bypass, an attacker can:

1. Intercept the HTTPS connection to the OCI registry
2. Present a fraudulent or self-signed certificate
3. Serve a malicious VM image containing backdoors or malware
4. The Podman machine would then run with the compromised image

The security patch corrects the TLS verification logic in the pull options:

// PullOptions includes data to alter certain knobs when pulling a source
// image.
type PullOptions struct {
-	// Require HTTPS and verify certificates when accessing the registry.
-	TLSVerify bool
+	// Skip TLS verification when accessing the registry.
+	SkipTLSVerify types.OptionalBool
	// [username[:password] to use when connecting to the registry.
	Credentials string
	// Quiet the progress bars when pushing.

Source: GitHub Podman Commit Update

Detection Methods for CVE-2025-6032

Indicators of Compromise

• Unusual network traffic patterns during podman machine init operations, particularly connections to unexpected IP addresses
• VM image checksums that do not match official registry manifests
• Certificate warnings or errors in network monitoring tools when Podman connects to registries
• Unexpected modifications to downloaded VM images in the Podman machine storage directories

Detection Strategies

• Monitor for podman machine init command executions and correlate with network traffic to identify potential MITM scenarios
• Implement network-level TLS inspection to detect certificate anomalies during container image pulls
• Deploy SentinelOne agents to detect suspicious process behavior following Podman machine initialization
• Use file integrity monitoring on Podman machine image storage locations

Monitoring Recommendations

• Enable verbose logging for Podman operations to capture registry connection details
• Monitor DNS queries for OCI registry endpoints to detect potential DNS-based MITM attacks
• Implement network segmentation to limit exposure of development workstations performing machine initialization
• Review Podman version inventories across the environment to identify vulnerable installations

How to Mitigate CVE-2025-6032

Immediate Actions Required

• Update Podman to a patched version that includes commit 726b506acc8a00d99f1a3a1357ecf619a1f798c3
• Apply relevant Red Hat security advisories for your distribution (RHSA-2025:9726, RHSA-2025:9751, RHSA-2025:9766, and related updates)
• Avoid running podman machine init on untrusted networks until patches are applied
• Verify integrity of any VM images previously downloaded using checksums from trusted sources

Patch Information

Red Hat has released multiple security advisories addressing this vulnerability across different product versions. Organizations should apply the appropriate update based on their deployment:

• Red Hat Security Advisory RHSA-2025:9726
• Red Hat Security Advisory RHSA-2025:9751
• Red Hat Security Advisory RHSA-2025:9766
• Red Hat Security Advisory RHSA-2025:10295

For complete details and the security fix, refer to the GitHub Podman Security Advisory GHSA-65gg-3w2w-hr4h.

Workarounds

• Only perform podman machine init operations on trusted, secured networks where MITM attacks are less feasible
• Pre-download and verify VM images from trusted sources before machine initialization
• Use network monitoring to detect and block suspicious certificate presentations during image downloads
• Consider using a local registry mirror with verified images for air-gapped or high-security environments

# Verify your Podman version and check for updates
podman --version

# On RHEL/CentOS/Fedora, update Podman to the patched version
sudo dnf update podman

# Verify the update was applied
rpm -q podman