CVE-2025-9566: Podman: podman kube play command may overwrite host files
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
Security readout for executives and security teams
Plain-English summary
A crafted Kubernetes configuration processed by Podman can cause a symbolic link inside a Secret or ConfigMap volume to overwrite a chosen host file. This could corrupt configuration or disrupt the host. The attacker cannot control the replacement content, and the supplied evidence does not claim data disclosure.
Executive priority
Treat this as high priority on systems that process externally supplied or multi-tenant deployment files. Prioritize identifying exposed automation and applying vendor updates. Systems that never use `podman kube play` have substantially lower practical exposure, but should still be inventoried because the potential outcome includes host-file corruption and service disruption.
Technical view
CVE-2025-9566 is a CWE-22 path-handling flaw in `podman kube play`. A symbolic link within a mounted Secret or ConfigMap volume can resolve to a host path and cause that file to be overwritten. The CVSS 3.1 score is 8.1, reflecting high integrity and availability impact without identified confidentiality impact.
Likely exposure
Exposure is highest where users or automation process attacker-influenced Kubernetes YAML with `podman kube play`. Upstream versions from 4.0.0 through versions before 5.6.1 are identified. The bundle also lists affected Red Hat packages with higher-looking versions, so downstream status must be checked against Red Hat advisories rather than semantic versions alone.
Exploitation context
The bundle reports no known active exploitation and marks KEV false. Exploitation requires an attacker-influenced kube file, a Secret or ConfigMap volume containing a symbolic link to a host path, and processing through `podman kube play`. The attacker selects the overwritten file but not the written content. Public exploit availability is not established by the supplied evidence.
Researcher notes
The attacker controls the destination file but not its resulting contents, limiting deterministic outcomes while retaining serious corruption and denial-of-service potential. Upstream introduction and fix points are 4.0.0 and 5.6.1. Because the affected list includes Red Hat builds whose visible versions exceed 5.6.1, package epoch, release, and advisory status are authoritative for downstream validation.
Mitigation direction
Upgrade upstream Podman to 5.6.1 or later; apply the applicable Red Hat advisory update for vendor packages.
Until updated, prevent `podman kube play` from processing untrusted or externally supplied kube files.
Restrict which users and automation can invoke `podman kube play` on sensitive hosts.
Review Secret and ConfigMap volume inputs for symbolic links targeting host paths.
Validation and detection
Inventory Podman versions and package release identifiers on systems using `podman kube play`.
Compare upstream installations with 5.6.1; assess Red Hat builds through applicable errata rather than semantic version alone.
Review automation and deployment workflows for `podman kube play` processing attacker-influenced YAML.
Inspect relevant Secret and ConfigMap volume sources for symbolic links resolving to host files.
After updating, confirm the installed vendor package matches the corrected build specified by its advisory.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.