High [CVE-2026-17107] Impersonation header injection in service-proxy grants cluster-admin on every managed cluster
This high-severity Red Hat Linux advisory covers CVE-2026-17107 affecting multicluster engine for Kubernetes 2.10, multicluster engine for Kubernetes 2.11, multicluster engine for Kubernetes 2.17.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Red Hat Linux publishes the next one.
See Red Hat Linux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
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. This is due to improper handling of impersonation group headers, enabling unauthorized administrative access.
While the impact of successful exploitation is severe, the attack requires authenticated access to the ACM hub cluster, which is a management-plane component not typically exposed to untrusted networks. Exploitation also depends on knowledge of the cluster-proxy architecture and deliberate construction of requests targeting specific managed clusters.
These prerequisites significantly reduce the likelihood of opportunistic or widespread exploitation. Red Hat severity: Important — CVSS 8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).
Weakness: CWE-441. Red Hat fixing advisory: RHSA-2026:46885, RHSA-2026:47388, RHSA-2026:47974, RHSA-2026:48284, RHSA-2026:47949, RHSA-2026:47735, RHSA-2026:47953.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · high-confidence parse· fetched 8 days ago·verify at source
- multicluster-engine/cluster-proxy-rhel9:1784342329
- multicluster-engine/cluster-proxy-rhel9:1784925025
- multicluster-engine/cluster-proxy-rhel9:1784926298
- multicluster-engine/cluster-proxy-rhel9:1783985960
- multicluster-engine/cluster-proxy-rhel9:1783278220
- RHSA-2026:46885
- RHSA-2026:47388
- RHSA-2026:47974
- RHSA-2026:48284
- RHSA-2026:47949
- RHSA-2026:47735
- RHSA-2026:47953
Official advisory · high-confidence parse· fetched 8 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official advisory · high-confidence parse· fetched 8 days ago·verify at source
More Red Hat Linux advisories
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.