Red Hat OpenShift CVE-2026-15584

Exploitation requires that the incluster-checks tool has been run and has created privileged debug pods with host-filesystem mounts in the shared default namespace, and that those pods are still present/running. The attacker must be an authenticated cluster user holding the standard 'edit' RBAC role (or higher) in that namespace, granting permission to kubectl exec into the pods. Limiting factors: authenticated tenant access is mandatory (not remote-unauthenticated), the privileged pods must exist (reflected in AC:H), and clusters that never run the tool or that isolate/restrict the default namespace are not exposed. No user interaction is required (UI:N).

The provided CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.5) and the description are partially inconsistent and should be reconciled by defenders. PR:L correctly reflects that a low-privileged but authenticated cluster user (edit role) is required - this is not a remote unauthenticated flaw. AV:N is defensible because kubectl exec traverses the API server over the network, but the attacker must already be an authenticated tenant, so real-world exposure is bounded by who holds edit in the default namespace. AC:H is appropriate because exploitation depends on the privileged debug pods actually existing, which only happens after incluster-checks has run. The score marks S:U (unchanged), yet escaping a pod to gain root on the host node arguably crosses a security scope boundary (S:C) - this understates blast radius, since node root compromises all co-located workloads. No EPSS score, KEV status, or POC was supplied, so exploitation likelihood cannot be quantified from the data; this reads as a real, high-impact insider/tenant-escalation issue rather than an internet-facing mass-exploitation risk. Verify scope and attack vector directly with the Red Hat advisory.

A developer with only the standard OpenShift 'edit' role in the default namespace notices privileged debug pods left behind by incluster-checks. They run kubectl exec into one of the pods, chroot into the mounted host filesystem, and plant credentials or a breakout payload to gain root on the worker node, pivoting to other tenants' workloads. No public POC is referenced in the available data.