Cross-namespace PVC disclosure via overprivileged view role
Published Jul 27, 2026 · Updated Aug 26, 2026
Authorization bypass in Red Hat OpenShift Virtualization allows remote authenticated users to clone any cluster PVC into a writable namespace. CDI accepts create permission on datavolumes/source from the aggregated view ClusterRole as sufficient clone authorization without requiring source-namespace write access. Exploitation requires a cluster-wide view binding plus edit or admin access to one namespace and discloses PVC contents across namespace boundaries.
Summary
What happened
Authorization bypass in Red Hat OpenShift Virtualization allows remote authenticated users to clone any cluster PVC into a writable namespace. CDI accepts create permission on datavolumes/source from the aggregated view ClusterRole as sufficient clone authorization without requiring source-namespace write access. Exploitation requires a cluster-wide view binding plus edit or admin access to one namespace and discloses PVC contents across namespace boundaries.
The record
- CVE
- CVE-2026-17527
- Published
- Jul 27, 2026
- Updated
- Aug 26, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Container Native Virtualization 4.20
- Classifications
- CWE-639, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 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