# CVE-2025-6032: GO-2025-3777 - Podman Improper Certificate Validation; machine missing TLS verification in github.com/containers/podman

Source: https://junglewise.ai/threats/cve-2025-6032-podman-improper-certificate-validation-machine-missing-tls  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-07-28  
License: CC BY 4.0 with a link back

CVE-2025-6032 · Severity: low · CVSS 3.1 · Published 2025-07-28

Podman Improper Certificate Validation; machine missing TLS verification in github.com/containers/podman

Technologies: [github.com/containers/podman (Go)](https://junglewise.ai/threats/technologies/github-com-containers-podman), [github.com/containers/podman/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-containers-podman-v2), [github.com/containers/podman/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-containers-podman-v3), [github.com/containers/podman/v4 (Go)](https://junglewise.ai/threats/technologies/github-com-containers-podman-v4), [github.com/containers/podman/v5 (Go)](https://junglewise.ai/threats/technologies/github-com-containers-podman-v5). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2025-6032 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-6032 being exploited in the wild.

**How severe is CVE-2025-6032?** Low severity, with a CVSS score of 3.1, published 28 July 2025.

**Which products and versions are affected?** github.com/containers/podman (Go) SEMVER:introduced=0; github.com/containers/podman/v2 (Go) SEMVER:introduced=0; github.com/containers/podman/v3 (Go) SEMVER:introduced=0; github.com/containers/podman/v4 (Go) SEMVER:introduced=4.8.0, SEMVER:introduced=4.8.0,last_affected=4.9.5; and 1 more.

**Is there a fix for CVE-2025-6032?** Yes. github.com/containers/podman/v5 (Go): upgrade to 5.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-6032?** Check whether you run github.com/containers/podman (Go), github.com/containers/podman/v2 (Go), github.com/containers/podman/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/containers/podman/v5 (Go): upgrade to 5.5.2 or later

  ```sh
  go get github.com/containers/podman/v5@v5.5.2
  ```


## Affected products

- github.com/containers/podman (Go) SEMVER:introduced=0
- github.com/containers/podman/v2 (Go) SEMVER:introduced=0
- github.com/containers/podman/v3 (Go) SEMVER:introduced=0
- github.com/containers/podman/v4 (Go) SEMVER:introduced=4.8.0, SEMVER:introduced=4.8.0,last_affected=4.9.5
- github.com/containers/podman/v5 (Go) SEMVER:introduced=0,fixed=5.5.2

## Identifiers

- CVE-2025-6032
- GHSA-65gg-3w2w-hr4h
- GO-2025-3777

## Related threats

- [Podman sandbox bypass via checkpoint image annotation](https://junglewise.ai/threats/cve-2026-94603-podman-the-podman-run-command-can-be-instructed-to-disable-almost)
- [Podman quadlet install incomplete file truncation](https://junglewise.ai/threats/cve-2026-19730-podman-quadlet-install-incomplete-file-truncation)
- [Podman host environment variable leak via malformed container image](https://junglewise.ai/threats/cve-2026-57231-podman-host-environment-variable-leak-via-malformed-container)
- [Podman symlink traversal in WORKDIR path resolution](https://junglewise.ai/threats/cve-2026-55686-podman-symlink-traversal-in-workdir-path-resolution)
- [Podman command injection in HyperV machine backend](https://junglewise.ai/threats/cve-2026-33414-podman-command-injection-in-hyperv-machine-backend)