OpenShift GitOps CVE-2025-13888

Requires an authenticated attacker who already holds namespace-admin privileges in a namespace on a cluster running Red Hat OpenShift GitOps (Argo CD operator) prior to v1.16.2. The attacker must be able to create ArgoCD Custom Resources that the operator reconciles; the flaw lets those CRs coerce the operator into granting permissions in other, including privileged, namespaces (the fix specifically restricts application of the openshift.io/cluster-monitoring namespace label to openshift- prefixed namespaces). Limiting factors: PR:H means single-tenant clusters or environments where namespace admins are already fully trusted see little added exposure; there is no unauthenticated or user-interaction path, and the primary risk is in multi-tenant/shared OpenShift clusters with semi-trusted tenants.

Signals conflict between a high paper severity and moderate real-world urgency. The vendor CVSS 3.1 base score is 9.1 (Critical) with vector AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, which I concur with: exploitation crosses a trust boundary (S:C) from a single namespace to the entire cluster, yielding full CIA impact (cluster root). However, PR:H is the critical tempering factor - the attacker must already hold namespace-admin privileges, so this is a privilege-escalation/lateral-movement primitive for an authenticated tenant, not an unauthenticated internet-facing RCE. EPSS is 0.69% (51st percentile), consistent with no public exploit and no active exploitation: there is no CISA KEV listing and no POC in the provided sources. No SSVC decision data was provided. The input Tag 'Information Disclosure' materially understates the flaw - this is full cluster takeover (privilege escalation to root), not mere disclosure. Net: a genuine priority for multi-tenant OpenShift clusters where namespace admins are semi-trusted, but the PR:H barrier and absence of exploitation evidence place it below internet-facing critical bugs.

A user holding namespace-admin rights on a single tenant namespace in a shared OpenShift cluster creates an ArgoCD Custom Resource crafted so the GitOps operator reconciles it with elevated, cross-namespace permissions (e.g., mislabeling privileged namespaces such as openshift- monitoring targets). Using those elevated permissions, the attacker deploys a privileged workload scheduled onto master/control-plane nodes, obtaining root over the whole cluster. No public exploit code is identified at time of analysis; exploitation requires an existing authenticated namespace-admin foothold.