Cluster-proxy: impersonation-header injection grants cluster-admin on every managed cluster (CVE-2026-17107)

Why this deserves its current priority

CVSS is 8.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 4, 2026

Sources and claim methodology

Upstream source description

A flaw was found in the cluster-proxy service-proxy component used in Red Hat Advanced Cluster Management for Kubernetes (RHACM) and multicluster-engine (MCE). The service-proxy appends impersonation group headers to proxied requests without first removing caller-supplied values, and the spoke ServiceAccount holds unrestricted impersonation permissions. An authenticated hub principal can inject an Impersonate-Group header to escalate to cluster-admin on every managed cluster.

Quoted source text, attributed separately from HOL analysis.