Cross-namespace resource injection via broker labels
Published Aug 20, 2026 · Updated Aug 20, 2026
Improper access control in Lighthouse in Red Hat Advanced Cluster Management for Kubernetes allows remote attackers to inject resources via broker metadata. The lighthouse-agent derives the destination namespace for replicated EndpointSlices and ServiceImports from a broker label or annotation that a compromised spoke cluster can control, and it does not validate that namespace before writing the objects. Reachability requires control of a spoke cluster rather than an external unauthenticated path, but successful exploitation can place service-discovery objects in peer namespaces, including kube-system and openshift-*, enabling privilege escalation, traffic disruption, or broader cluster compromise.
Summary
What happened
Improper access control in Lighthouse in Red Hat Advanced Cluster Management for Kubernetes allows remote attackers to inject resources via broker metadata. The lighthouse-agent derives the destination namespace for replicated EndpointSlices and ServiceImports from a broker label or annotation that a compromised spoke cluster can control, and it does not validate that namespace before writing the objects. Reachability requires control of a spoke cluster rather than an external unauthenticated path, but successful exploitation can place service-discovery objects in peer namespaces, including kube-system and openshift-*, enabling privilege escalation, traffic disruption, or broader cluster compromise.
The record
- CVE
- CVE-2026-66788
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Advanced Cluster Management for Kubernetes
- Classifications
- CWE-284, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 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