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
Podman can overwrite files on the host when podman kube play handles certain Secret or ConfigMap volume mounts containing symlinks. An attacker cannot choose the replacement content, but can choose which host file is overwritten. That creates meaningful integrity and availability risk on hosts or pipelines that process untrusted Kubernetes YAML.
Executive priority
Prioritize remediation for build systems, container hosts, and automation paths that process Kubernetes YAML from users or external repositories. This is not confirmed exploited, but the impact can disrupt host integrity or availability.
Technical view
CVE-2025-9566 is a CWE-22 flaw in podman kube play, introduced upstream in v4.0.0 and fixed in v5.6.1. The issue involves Secret or ConfigMap volume mounts containing symbolic links to host paths. Red Hat lists multiple affected RHEL and OpenShift-related packages.
Likely exposure
Exposure is highest where users, automation, or CI/CD systems run podman kube play against manifests from less-trusted sources. Red Hat lists affected podman packages across RHEL 8, RHEL 9, RHEL 10, and OpenShift Container Platform 4.12 related packages.
Exploitation context
The bundle rates this CVSS 8.1 with low complexity, low privileges, no user interaction, and high integrity and availability impact. KEV is false, and the supplied sources do not show confirmed active exploitation.
Researcher notes
The source evidence is strong for affected versions and high-level behavior, but incomplete for exploit prevalence and detailed fixed-package mapping. Avoid assuming content control: the bundle says the attacker controls the target file, not the written content.
Mitigation direction
Update Podman to upstream v5.6.1 or vendor-fixed packages.
Apply relevant Red Hat RHSA or RHBA advisories for affected platforms.
Restrict who can submit manifests to podman kube play workflows.
Avoid processing untrusted Kubernetes YAML with podman kube play.
Check vendor guidance for platform-specific fixes and constraints.
Validation and detection
Inventory Podman versions and compare against v5.6.1 fixed upstream version.
Check Red Hat package versions against listed affected advisories.
Identify automation that runs podman kube play on external manifests.
Review Secret and ConfigMap mounts for unexpected symlink content.
Verify patched hosts no longer run affected package builds.
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
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.