Container file disclosure via PVC symlink following
Published Nov 7, 2025 · Updated Nov 7, 2025
Path traversal in KubeVirt before 1.5.3 and KubeVirt 1.6.0 allows remote authenticated users to read virt-launcher pod files. The host-disk PVC mount code follows attacker-created symlinks outside the volume, changes the target file to UID 107, and exposes it as a libvirt block device. Exploitation requires control over PVC contents and the ability to attach that PVC to a VM; the result is confidentiality loss only.
Summary
What happened
Path traversal in KubeVirt before 1.5.3 and KubeVirt 1.6.0 allows remote authenticated users to read virt-launcher pod files. The host-disk PVC mount code follows attacker-created symlinks outside the volume, changes the target file to UID 107, and exposes it as a libvirt block device. Exploitation requires control over PVC contents and the ability to attach that PVC to a VM; the result is confidentiality loss only.
The record
- CVE
- CVE-2025-64433
- Published
- Nov 7, 2025
- Updated
- Nov 7, 2025
- Vendor
- KubeVirt
- Product
- KubeVirt
- Classifications
- CWE-200, CWE-22, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 7, 2025CVE publishedPublication date reported by the CVE source.
- Nov 7, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.3
- Affected versionversion=>= 1.6.0-alpha.0, < 1.6.1
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
- KubeVirt arbitrary container file-read proof of conceptproof of concept · demonstrated
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