# CVE-2025-9566: Podman: podman kube play command may overwrite host files > An attacker can overwrite arbitrary host files via symbolic links in ConfigMap or Secret volumes when using the podman kube play command. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Sep 2025 - **Updated:** 8 Oct 2026 - **Also known as:** ALSA-2025:15900, ALSA-2025:15901, ALSA-2025:15904, AZL-67046, AZL-67049, BELL-CVE-2025-9566, CLSA-2025-1759505734, DEBIAN-CVE-2025-9566, GHSA-wp3j-xq48-xpjw, GO-2025-3935, MINI-v4cx-4747-j7xx, RHBA-2025:15692, RHBA-2025:15712, RHBA-2025:16158, RHBA-2025:16163, RHEA-2025:4782, RHSA-2025:15900, RHSA-2025:15901, RHSA-2025:16480, RHSA-2025:16481, RHSA-2025:16482, RHSA-2025:16488, RHSA-2025:16515, RHSA-2026:18289, RHSA-2026:18722, RLSA-2025:15900, RLSA-2025:15901, RLSA-2026:18722, SUSE-SU-2025:03534-1, SUSE-SU-2025:03584-1, SUSE-SU-2025:20899-1, SUSE-SU-2025:3782-1, UBUNTU-CVE-2025-9566 ## What is CVE-2025-9566? CVE-2025-9566 is a high-severity path traversal vulnerability in Red Hat Enterprise Linux 10, published on 5 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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 Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-9566? 9 open source packages ship an affected version, including github.com/containers/podman/v4, github.com/containers/podman and github.com/containers/podman/v2. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/containers/podman/v4` | Go | All versions | None | | `github.com/containers/podman/v4` | Go | All versions to 4.9.5 | None | | `github.com/containers/podman/v4` | Go | All versions to 4.9.5 | None | | `github.com/containers/podman` | Go | All versions | None | | `github.com/containers/podman/v2` | Go | All versions | None | | `github.com/containers/podman/v3` | Go | All versions | None | | `github.com/containers/podman/v5` | Go | All versions | 5.6.1 | | `github.com/containers/podman/v5` | Go | All versions | 5.6.1 | | `github.com/containers/podman/v5` | Go | All versions | 5.6.1 | | `podman-docker` | AlmaLinux:10 | All versions | 6:5.4.0-13.el10_0 | | `aardvark-dns` | AlmaLinux:8 | All versions | 2:1.10.1-2.module_el8.10.0+3909+6e1c1eb7 | | `aardvark-dns` | AlmaLinux:8 | All versions | 2:1.10.1-2.module_el8.10.0+4023+db236c53 | | `aardvark-dns` | AlmaLinux:8 | All versions | 2:1.10.1-2.module_el8.10.0+4047+545787c4 | | `buildah` | AlmaLinux:8 | All versions | 2:1.33.12-2.module_el8.10.0+4016+efd18bf8 | | `buildah` | AlmaLinux:8 | All versions | 2:1.33.12-2.module_el8.10.0+4023+db236c53 | | `buildah` | AlmaLinux:8 | All versions | 2:1.33.12-2.module_el8.10.0+4047+545787c4 | | `buildah-tests` | AlmaLinux:8 | All versions | 2:1.33.12-2.module_el8.10.0+4047+545787c4 | | `cockpit-podman` | AlmaLinux:8 | All versions | 84.1-1.module_el8.10.0+4016+efd18bf8 | | `conmon` | AlmaLinux:8 | All versions | 3:2.1.10-1.module_el8.10.0+3970+8445edf6 | | `container-selinux` | AlmaLinux:8 | All versions | 2:2.229.0-2.module_el8.10.0+3909+6e1c1eb7 | | `containernetworking-plugins` | AlmaLinux:8 | All versions | 1:1.4.0-6.module_el8.10.0+4016+efd18bf8 | | `containernetworking-plugins` | AlmaLinux:8 | All versions | 1:1.4.0-6.module_el8.10.0+4023+db236c53 | | `containernetworking-plugins` | AlmaLinux:8 | All versions | 1:1.4.0-6.module_el8.10.0+4047+545787c4 | | `containers-common` | AlmaLinux:8 | All versions | 2:1-82.module_el8.10.0+3876+e55593a8 | | `containers-common` | AlmaLinux:8 | All versions | 2:1-82.module_el8.10.0+3901+4b80ecd7 | | `containers-common` | AlmaLinux:8 | All versions | 2:1-82.module_el8.10.0+3970+8445edf6 | | `containers-common` | AlmaLinux:8 | All versions | 2:1-82.module_el8.10.0+4047+545787c4 | | `crit` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3845+87b84552 | | `crit` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3858+6ad51f9f | | `crit` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3901+4b80ecd7 | | `crit` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+4047+545787c4 | | `criu` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3876+e55593a8 | | `criu` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3909+6e1c1eb7 | | `criu` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3926+f12484f5 | | `criu` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3970+8445edf6 | | `criu-devel` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3858+6ad51f9f | | `criu-devel` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3876+e55593a8 | | `criu-devel` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+4016+efd18bf8 | | `criu-devel` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+4023+db236c53 | | `criu-libs` | AlmaLinux:8 | All versions | 3.18-5.module_el8.10.0+3909+6e1c1eb7 | ## How do I fix CVE-2025-9566? Upgrade to a fixed version. ## Is CVE-2025-9566 being exploited? There is no known exploitation of CVE-2025-9566 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-9566 and fix it if it is affected. What it is: CVE-2025-9566 is a high-severity path traversal vulnerability in Red Hat Enterprise Linux 10, published on 5 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-9566 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/containers/podman/v4 (Go): affected all versions; no fix listed - github.com/containers/podman/v4 (Go): affected all versions up to 4.9.5; no fix listed - github.com/containers/podman/v4 (Go): affected all versions up to 4.9.5; no fix listed - github.com/containers/podman (Go): affected all versions; no fix listed - github.com/containers/podman/v2 (Go): affected all versions; no fix listed - github.com/containers/podman/v3 (Go): affected all versions; no fix listed - github.com/containers/podman/v5 (Go): affected all versions; fixed in 5.6.1 - github.com/containers/podman/v5 (Go): affected all versions; fixed in 5.6.1 - github.com/containers/podman/v5 (Go): affected all versions; fixed in 5.6.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-9566/ (Markdown: https://insights.sbomify.com/CVE-2025-9566/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9566 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9566 - OSV: https://osv.dev/vulnerability/CVE-2025-9566 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-9566/ Summaries are generated and may contain mistakes; the official description above is the record.