How severe is CVE-2025-6032?

CVE-2025-6032 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-6032?

CVE-2025-6032 affects the following packages: github.com/containers/podman/v4 (Go), github.com/containers/podman/v5 (Go). Ecosystems affected: Go.

How do I fix CVE-2025-6032?

A fix is available for CVE-2025-6032; check the affected-versions list above or the advisory for the patched release of github.com/containers/podman/v4, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2025-6032 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/podman/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-6032 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-6032 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-6032 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-6032?

CVE-2025-6032 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-6032?

CVE-2025-6032 is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-6032 published, and has it been updated?

CVE-2025-6032 was published on June 24, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2025-6032 — podman

HIGHFix: containers/podman@726b506

CVE-2025-6032 is a high-severity (CVSS 8.3) CWE-295 vulnerability in github.com/containers/podman/v4. A fix is available for github.com/containers/podman/v4 — see the affected versions and patch details below.

Podman: podman missing tls verification

Also known asGHSA-65gg-3w2w-hr4hGO-2025-3777

Published

Jun 24, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-6032.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐹github.com/containers/podman/v4🐹github.com/containers/podman/v5

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The podman machine init command fails to verify the TLS certificate when downloading the VM images from an OCI registry (which it does by default since 5.0.0) allowing a possible Man In The Middle attack.

Patches

https://github.com/containers/podman/commit/726b506acc8a00d99f1a3a1357ecf619a1f798c3 Fixed in v5.5.2

Workarounds

Download the disk image manually via some other tool that verifies the TLS connection. Then pass the local image as file path (podman machine init --image ./somepath)

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/containers/podman/v4`	≥ 4.8.0	No fix
🐹Go	`github.com/containers/podman/v5`	all versions	5.5.2`go get github.com/containers/podman/v5@v5.5.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/podman/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2025-6032; check the affected-versions list above or the advisory for the patched release of github.com/containers/podman/v4, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

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. This allows a remote attacker with access to the network path between the registry and the client to perform a Man In the Middle attack.

Workaround published by Red Hat

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>

Source: Red Hat security advisory for CVE-2025-6032 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`podman-6:5.4.0-12.el10_0`	RHSA-2025:10549
Red Hat Enterprise Linux 8	`container-tools:rhel8-8100020250625105344.afee755d`	RHSA-2025:10551
Red Hat Enterprise Linux 9	`podman-5:5.4.0-12.el9_6`	RHSA-2025:10550
Red Hat Enterprise Linux 9.4 Extended Update Support	`podman-4:4.9.4-18.el9_4.2`	RHSA-2025:10668
Red Hat OpenShift Container Platform 4.16	`podman-4:4.9.4-14.rhaos4.16.el8`	RHSA-2025:9766
Red Hat OpenShift Container Platform 4.16	`openshift/ose-rhel-coreos-9:416.94.202507222002-0`	RHSA-2025:11681
Red Hat OpenShift Container Platform 4.17	`podman-5:5.2.2-8.rhaos4.17.el8`	RHSA-2025:10295
Red Hat OpenShift Container Platform 4.17	`openshift/ose-rhel-coreos-9:417.94.202507132309-0`	RHSA-2025:11359

Frequently Asked Questions

### Impact The podman machine init command fails to verify the TLS certificate when downloading the VM images from an OCI registry (which it does by default since 5.0.0) allowing a possible Man In The Middle attack. ### Patches https://github.com/containers/podman/commit/726b506acc8a00d99f1a3a1357ecf619a1f798c3 Fixed in v5.5.2 ### Workarounds Download the disk image manually via some other tool that verifies the TLS connection. Then pass the local image as file path (podman machine init --image ./somepath)

O3 Security · Impact-Aware SCA

Is CVE-2025-6032 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works