CVE-2026-17107

HIGHPre-NVD 8.58.5—
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.5
EG Score
8.5(high)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

July 24, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 24, 2026
Patch available. Sources: redhat.
redhat

2506771 – (CVE-2026-17107) CVE-2026-17107 cluster-proxy: cluster-proxy: Impersonation header injection in service-proxy grants cluster-admin on every managed cluster

https://bugzilla.redhat.com/show_bug.cgi?id=2506771
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-17107

Vendor Advisories for CVE-2026-17107(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 11:45 UTCGHSA enrichment
  2. 2026-07-27 00:49 UTCEG score recompute
  3. 2026-07-27 00:49 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 13:52 UTCEG score recompute
  7. 2026-07-26 13:52 UTCGHSA enrichment
  8. 2026-07-26 02:55 UTCEG score recompute
  9. 2026-07-26 02:55 UTCGHSA enrichment
  10. 2026-07-25 14:17 UTCEPSS rescore
  11. 2026-07-25 14:17 UTCEPSS rescore
  12. 2026-07-24 19:07 UTCEG score recompute
  13. 2026-07-24 19:06 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-17107?
CVE-2026-17107 is a high vulnerability published on July 24, 2026. 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…
When was CVE-2026-17107 disclosed?
CVE-2026-17107 was first published in the National Vulnerability Database on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17107 actively exploited?
CVE-2026-17107 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.5% of all scored CVEs.
What is the CVSS score of CVE-2026-17107?
CVE-2026-17107 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-17107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17107, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17107

Explore →

Is Your Infrastructure Affected by CVE-2026-17107?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs