CVE-2026-171078.5HighCWE-441

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

Red Hat · multicluster engine for Kubernetes 2.10

Vendor fix available · Affected: Red Hat multicluster engine for Kubernetes 2.10 · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.6%probability of exploitation in the next 30 days

47th percentile

050100

Higher than 47% of scored CVEs

8.5HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products7

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Red Hat · multicluster engine for Kubernetes 2.10Versions not stated
Red Hat · multicluster engine for Kubernetes 2.10Versions not stated
Red Hat · multicluster engine for Kubernetes 2.11Versions not stated
Red Hat · multicluster engine for Kubernetes 2.17Versions not stated
Red Hat · multicluster engine for Kubernetes 2.6Versions not stated
Red Hat · multicluster engine for Kubernetes 2.8Versions not stated
Red Hat · multicluster engine for Kubernetes 2.9Versions not stated

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Unintended Proxy or Intermediary · Access Control
Vendor: Red Hat
Published: July 2026
Band: Unlikely (under 1%), July 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-17107 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.