Node-root escalation via shared privileged debug pods
Published Jul 13, 2026 · Updated Jul 13, 2026
Privilege escalation in Red Hat Pen Drive powered by Red Hat Lightspeed allows remote authenticated users to gain node root access. Incluster-checks creates privileged oc debug pods in the shared default namespace with host filesystem access, exposing their exec interface to namespace editors. An OpenShift account with the standard edit role must wait for a scan to create one of these pods; successful access grants root control of cluster nodes and their workloads.
Summary
What happened
Privilege escalation in Red Hat Pen Drive powered by Red Hat Lightspeed allows remote authenticated users to gain node root access. Incluster-checks creates privileged oc debug pods in the shared default namespace with host filesystem access, exposing their exec interface to namespace editors. An OpenShift account with the standard edit role must wait for a scan to create one of these pods; successful access grants root control of cluster nodes and their workloads.
The record
- CVE
- CVE-2026-15584
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- 389 Directory Server
- Product
- Pen Drive powered by Red Hat Lightspeed
- Classifications
- CWE-250, T1611
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 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.
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