Host file overwrite via volume symlink following
Published Sep 5, 2025 · Updated Sep 10, 2026
Symlink traversal in Red Hat Podman 4.0.0 through 5.6.0 allows remote authenticated users to overwrite host files during kube play. ConfigMap and Secret population joins each YAML key to the volume mount and opens the resulting path while following an existing symlink outside the volume. Exploitation requires reuse of the same volume after a malicious container creates the symlink; the attacker chooses the target path, but the YAML author controls the written content.
Summary
What happened
Symlink traversal in Red Hat Podman 4.0.0 through 5.6.0 allows remote authenticated users to overwrite host files during kube play. ConfigMap and Secret population joins each YAML key to the volume mount and opens the resulting path while following an existing symlink outside the volume. Exploitation requires reuse of the same volume after a malicious container creates the symlink; the attacker chooses the target path, but the YAML author controls the written content.
The record
- CVE
- CVE-2025-9566
- Published
- Sep 5, 2025
- Updated
- Sep 10, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift Container Platform 4.16
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 2025CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo