CVE-2026-10533: Openshift: openshift: non-admin user can bypass resourcequota and flood etcd with events causing cluster-wide api degradation

Published Jun 1, 2026
·
Updated

A flaw was found in OpenShift Container Platform. Completed pods with restartPolicy: Never do not count toward ResourceQuota pod limits, and Kubernetes events are not quota-scoped. A non-privileged user who can create pods in a namespace can exploit this to generate a large volume of events that accumulate in etcd, causing API server performance degradation across the cluster.

Other sources

The OpenShift Container Platform ResourceQuota controller does not count completed pods (restartPolicy: Never, phase Succeeded) against the pod quota. Additionally, Kubernetes events generated by pod lifecycle operations are not subject to any quota or rate limit. A non-admin user with pod creation privileges can deploy a control pod using the default deployer ServiceAccount that continuously spawns short-lived child pods (150ms sleep, then complete). Each child pod generates events, frees its quota slot on completion, and allows the next pod to be created. In testing, a single control pod generates approximately 43,000 events per hour. With a 3-hour event TTL, this produces ~130,000 events from a single namespace, which is sufficient to cause etcd pressure and API server degradation. The attack requires only the ability to deploy a pod — no elevated privileges, quota changes, or cross-namespace access. An administrator can remediate by deleting events and completed pods, and events expire naturally via the 3-hour TTL.

Red Hat

Affected Software

2 affected components
Red Hat OpenShift Container Platform
redhat OpenShift Container Platform=4.0

Event History

Jun 1, 2026
Data Sourced
via Red Hat·11:42 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·01:19 PM
Data Sourced
via MITRE·01:19 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-10533?

The severity of CVE-2026-10533 is rated as medium with a score of 5.

2

How does CVE-2026-10533 affect OpenShift users?

CVE-2026-10533 allows non-admin users to bypass resource quota limits and flood etcd with events, causing API degradation.

3

What versions of OpenShift are affected by CVE-2026-10533?

CVE-2026-10533 affects the OpenShift Container Platform, particularly versions prior to the fix related to this vulnerability.

4

How can I mitigate the impact of CVE-2026-10533?

Mitigation of CVE-2026-10533 involves restricting non-privileged users' ability to create pods in namespaces or applying available patches.

5

Is there a fix available for CVE-2026-10533?

Yes, fixes for CVE-2026-10533 are usually included in updates for the OpenShift Container Platform, so users should apply the latest patches.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203