High [CVE-2025-9566] Podman: podman kube play command may overwrite host files
This high-severity Red Hat Linux advisory covers CVE-2025-9566 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.6 Telecommunications Update Service.
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.
Summary
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 The Red Hat Product Security team has evaluated this vulnerability as having the Important severity.
This happens because of the consequences of an successful attack and the low complexity (AC:L) on exploiting this vulnerability.
Although the attacker cannot control the content written to the target file, depending on which file was targeted, the exploitation of this flaw may lead sensitive data corruption (I:H) and leading the system to crash resulting in a Denial of Service attack (A:H). Weakness: CWE-22.
Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support; Red Hat Enterprise Linux 8.6 Telecommunications Update Service; Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions; and 16 more.
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
- podman-6:5.4.0-13.el10_0
- podman-7:5.6.0-5.el10_1
- podman-7:5.8.0-2.el10
- container-tools:rhel8-8100020250911075811.afee755d
- container-tools:rhel8-8060020250919150821.3b538bd8
- container-tools:rhel8-8080020250919060528.0f77c1b7
- podman-5:5.4.0-13.el9_6
- podman-6:5.6.0-6.el9_7
- podman-6:5.8.0-1.el9
- podman-2:4.2.0-6.el9_0.5
- podman-2:4.4.1-22.el9_2.4
- podman-4:4.9.4-18.el9_4.3
- rhcos-412.86.202510291903-0
- rhcos-413.92.202510150118-0
- kernel-0:5.14.0-284.138.1.el9_2
- kernel-rt-0:5.14.0-284.138.1.rt14.423.el9_2
- podman-3:4.4.1-23.rhaos4.14.el8
- rhcos-414.92.202510211419-0
- podman-3:4.4.1-35.rhaos4.15.el8
- rhcos-417.94.202510112152-0
- container-selinux-4:2.237.0-1.rhaos4.18.el9
- cri-o-0:1.31.12-3.rhaos4.18.gitdc59c78.el8
- kernel-0:5.14.0-427.87.1.el9_4
- openshift-0:4.18.0-202509090932.p2.ga4cad44.assembly.stream.el8
- openshift-ansible-0:4.18.0-202509011551.p2.g018e43a.assembly.stream.el8
- podman-5:5.2.2-11.rhaos4.18.el9
- rhcos-418.94.202510230424-0
- container-selinux-4:2.237.0-1.rhaos4.19.el9
- cri-o-0:1.32.8-3.rhaos4.19.git60d4e21.el9
- openshift-0:4.19.0-202509070341.p2.gb5229e8.assembly.stream.el9
- podman-5:5.4.0-7.rhaos4.19.el9
- rhcos-4.19.9.6.202510140714-0
- podman-5:5.4.0-12.rhaos4.20.el9
- rhcos-4.20.9.6.202510220229-0
- podman-main-5.8.2-1.hum1
- devspaces/udi-base-rhel9:3.24-1760921292
- devspaces/udi-rhel9:3.24-1761160160
- RHSA-2025:15901
- RHSA-2025:20983
- RHSA-2026:18289
- RHSA-2025:15904
- RHSA-2025:16482
- RHSA-2025:16515
- RHSA-2025:15900
- RHSA-2025:20909
- RHSA-2026:18722
- RHSA-2025:16480
- RHSA-2025:16488
- RHSA-2025:16481
- RHSA-2025:19894
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- Red Hat advises to not run the podman kube play command with untrusted Kubernetes YAML file as input, additionally review the Kubernetes YAML file before running it through podman may help to catch maliciously crafted secretes or volumes that may be used to exploit this vulnerability.
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.