The vulnerability in Red Hat OpenShift Container Platform 4 involves improper resource quota enforcement for completed pods with restartPolicy: Never and unscoped Kubernetes events. Because these pods do not count against ResourceQuota pod limits and events are not quota-scoped, a non-privileged user can create many pods that generate excessive events. These events accumulate in etcd, the Kubernetes backing store, causing performance degradation of the API server cluster-wide. This is a denial-of-service type issue impacting availability but does not affect confidentiality or integrity.

The impact is limited to availability degradation of the OpenShift API server due to resource exhaustion in etcd from excessive Kubernetes events generated by completed pods not counted against quotas. There is no impact on confidentiality or integrity. The vulnerability requires a non-privileged user to have pod creation rights in a namespace. There are no known exploits in the wild at this time.

Patch status is not yet confirmed — check the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-10533 for current remediation guidance. Until an official fix is available, consider restricting pod creation permissions to trusted users and monitor for unusual event volume. No vendor advisory states that the issue is already mitigated or requires no action.