Cluster-wide API degradation via unscoped event flooding
Published Jun 1, 2026 · Updated Jun 1, 2026
Resource exhaustion in Red Hat OpenShift Container Platform 4 allows remote authenticated users to degrade cluster API performance. Completed pods configured with restartPolicy: Never stop counting against pod ResourceQuota, while Kubernetes events remain outside quota scope and accumulate in etcd. Namespace-level pod creation permission is sufficient to flood persistent event storage and slow API operations across the cluster.
Summary
What happened
Resource exhaustion in Red Hat OpenShift Container Platform 4 allows remote authenticated users to degrade cluster API performance. Completed pods configured with restartPolicy: Never stop counting against pod ResourceQuota, while Kubernetes events remain outside quota scope and accumulate in etcd. Namespace-level pod creation permission is sufficient to flood persistent event storage and slow API operations across the cluster.
The record
- CVE
- CVE-2026-10533
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift Container Platform
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 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