The vulnerability in Red Hat OpenShift Container Platform 4 arises because completed pods configured with restartPolicy: Never are excluded from ResourceQuota pod limits, and Kubernetes events are not limited by quota. This flaw permits a non-privileged user who can create pods in a namespace to generate a large volume of Kubernetes events. These events accumulate in etcd, the cluster's backing store, which can degrade the API server's performance cluster-wide. The issue impacts availability but does not affect confidentiality or integrity. The CVSS 3.1 base score is 5.0 (medium severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, and scope change. No patch or official remediation guidance is currently provided by Red Hat in the advisory.

The vulnerability impacts the availability of the OpenShift cluster by allowing resource exhaustion in etcd due to unbounded event accumulation. This can degrade API server performance across the cluster, potentially affecting cluster operations and responsiveness. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.

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 only and monitor cluster performance for signs of resource exhaustion. Avoid relying on ResourceQuota pod limits alone to control resource usage for pods with restartPolicy: Never. No vendor advisory states that no action is required or that the issue is already mitigated.