Most recent entries from all

ALSA-2025:15900 — Important: podman security update

Affected: AlmaLinux:9: podman, AlmaLinux:9: podman-docker, AlmaLinux:9: podman-plugins, AlmaLinux:9: podman-remote, AlmaLinux:9: podman-tests

The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.

Security Fix(es):

* podman: Podman kube play command may overwrite host files (CVE-2025-9566)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

bdu:2025-13147

BELL-CVE-2025-9566

Affected: Alpaquita:23: podman, Alpaquita:25: podman, Alpaquita:stream: podman

EUVD-2026-377382

fkie_cve-2025-9566

There's a vulnerability in podman where an attacker may use the kube play command to overwrite host files when the kube file container a Secrete or a ConfigMap volume mount and such volume contains a symbolic link to a host file path. In a successful attack, the attacker can only control the target file to be overwritten but not the content to be written into the file.

Binary-Affected: podman Upstream-version-introduced: v4.0.0 Upstream-version-fixed: v5.6.1

GHSA-wp3j-xq48-xpjw — podman kube play symlink traversal vulnerability

Affected: Go: github.com/containers/podman/v5, Go: github.com/containers/podman/v4

### Impact

The podman kube play command can overwrite host files when the kube file contains a ConfigMap or Secret volume mount and the volume already contains a symlink to a host file. This allows a malicious container to write to arbitrary files on the host BUT the attacker only controls the target path not the contents that will be written to the file. The contents are defined in the yaml file by the end user.

### Requirements to exploit: podman kube play must be used with a ConfigMap or Secret volume mount AND must be run more than once on the same volume. All the attacker has to do is create the malicious symlink on the volume the first time it is started. After that all following starts would follow the symlink and write to the host location.

### Patches Fixed in podman v5.6.1 https://github.com/containers/podman/commit/43fbde4e665fe6cee6921868f04b7ccd3de5ad89

### Workarounds

Don't use podman kube play with ConfigMap or Secret volume mounts.

### PR with test for CI

Adding on 9/8/2025 by @TomSweeneyRedHat , this is the PR containing the test in CI: https://github.com/containers/podman/pull/27001

msrc_CVE-2025-9566 — Podman: podman kube play command may overwrite host files

msrc_CVE-2025-9566

openSUSE-SU-2025:15538-1 — govulncheck-vulndb-0.0.20250908T141310-1.1 on GA media

govulncheck-vulndb-0.0.20250908T141310-1.1 on GA media

RHBA-2025:15692 — Red Hat Bug Fix Advisory: OpenShift Container Platform 4.19.12 packages update

podman: Podman kube play command may overwrite host files

SUSE-SU-2025:03534-1 — Security update for podman

Security update for podman

UBUNTU-CVE-2025-9566

Affected: Ubuntu:Pro:24.04:LTS: libpod, Ubuntu:25.10: podman, Ubuntu:26.04:LTS: podman

WID-SEC-W-2025-1974 — Podman: Schwachstelle ermöglicht Manipulation von Dateien

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Podman ausnutzen, um Dateien zu manipulieren.