CVE-2026-17107

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM 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

A fix is available — apply it.

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(medium)
EG Risk
38(Track)
EG Risk 38/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 24, 2026

Last Modified

September 8, 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(8)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-engine/cluster-proxy-rhel9:17839859602026-07-29redhat
redhatmulticluster-engine/cluster-proxy-rhel9:17843423292026-07-29redhat
redhatmulticluster-engine/cluster-proxy-rhel9:17849250252026-07-29redhat
redhatmulticluster-engine/cluster-proxy-rhel9:17849262982026-07-29redhat
redhatmulticluster-engine/cluster-proxy-rhel9:17832782202026-07-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 165× 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.

Showing the most recent 100 of 398 total refreshes for this CVE.

  1. 2026-09-18 22:27 UTCEG score recompute
  2. 2026-09-18 22:27 UTCVendor advisory
  3. 2026-09-18 22:27 UTCGHSA enrichment
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-18 02:58 UTCEG score recompute
  6. 2026-09-18 02:58 UTCVendor advisory
  7. 2026-09-18 02:58 UTCGHSA enrichment
  8. 2026-09-17 01:58 UTCEG score recompute
  9. 2026-09-17 01:58 UTCVendor advisory
  10. 2026-09-17 01:58 UTCGHSA enrichment
  11. 2026-09-16 14:07 UTCEPSS rescore
  12. 2026-09-16 06:39 UTCEG score recompute
  13. 2026-09-16 06:39 UTCVendor advisory
  14. 2026-09-16 06:39 UTCGHSA enrichment
  15. 2026-09-16 05:14 UTCEPSS rescore
  16. 2026-09-15 09:35 UTCEG score recompute
  17. 2026-09-15 09:35 UTCVendor advisory
  18. 2026-09-15 09:35 UTCGHSA enrichment
  19. 2026-09-14 10:15 UTCVendor advisory
  20. 2026-09-14 10:15 UTCGHSA enrichment
  21. 2026-09-13 23:16 UTCEG score recompute
  22. 2026-09-13 23:16 UTCVendor advisory
  23. 2026-09-13 23:16 UTCGHSA enrichment
  24. 2026-09-13 16:46 UTCEPSS rescore
  25. 2026-09-13 12:20 UTCVendor advisory
Show 75 more
  1. 2026-09-13 12:20 UTCGHSA enrichment
  2. 2026-09-13 01:24 UTCEG score recompute
  3. 2026-09-13 01:24 UTCVendor advisory
  4. 2026-09-13 01:24 UTCGHSA enrichment
  5. 2026-09-12 15:00 UTCEPSS rescore
  6. 2026-09-12 14:28 UTCVendor advisory
  7. 2026-09-12 14:28 UTCGHSA enrichment
  8. 2026-09-12 03:32 UTCVendor advisory
  9. 2026-09-12 03:32 UTCGHSA enrichment
  10. 2026-09-11 16:36 UTCEG score recompute
  11. 2026-09-11 16:36 UTCVendor advisory
  12. 2026-09-11 16:36 UTCGHSA enrichment
  13. 2026-09-11 14:52 UTCEPSS rescore
  14. 2026-09-11 09:36 UTCEPSS rescore
  15. 2026-09-11 02:32 UTCVendor advisory
  16. 2026-09-11 02:32 UTCGHSA enrichment
  17. 2026-09-10 13:35 UTCEG score recompute
  18. 2026-09-10 13:35 UTCVendor advisory
  19. 2026-09-10 13:35 UTCGHSA enrichment
  20. 2026-09-10 09:34 UTCEPSS rescore
  21. 2026-09-09 08:44 UTCEG score recompute
  22. 2026-09-09 08:44 UTCVendor advisory
  23. 2026-09-09 08:44 UTCGHSA enrichment
  24. 2026-09-08 22:00 UTCEPSS rescore
  25. 2026-09-08 16:13 UTCVendor advisory
  26. 2026-09-08 16:13 UTCGHSA enrichment
  27. 2026-09-08 12:38 UTCEG score recompute
  28. 2026-09-08 12:38 UTCVendor advisory
  29. 2026-09-08 12:38 UTCGHSA enrichment
  30. 2026-09-08 11:46 UTCEG score recompute
  31. 2026-09-08 11:46 UTCVendor advisory
  32. 2026-09-08 11:46 UTCGHSA enrichment
  33. 2026-09-07 19:26 UTCEG score recompute
  34. 2026-09-07 19:26 UTCVendor advisory
  35. 2026-09-07 19:26 UTCGHSA enrichment
  36. 2026-09-07 18:30 UTCEG score recompute
  37. 2026-09-07 18:30 UTCVendor advisory
  38. 2026-09-07 18:30 UTCGHSA enrichment
  39. 2026-09-07 16:01 UTCEPSS rescore
  40. 2026-09-06 18:24 UTCEG score recompute
  41. 2026-09-06 18:24 UTCVendor advisory
  42. 2026-09-06 18:24 UTCGHSA enrichment
  43. 2026-09-06 13:47 UTCEPSS rescore
  44. 2026-09-06 13:14 UTCVendor advisory
  45. 2026-09-06 13:14 UTCGHSA enrichment
  46. 2026-09-06 02:17 UTCEG score recompute
  47. 2026-09-06 02:17 UTCVendor advisory
  48. 2026-09-06 02:17 UTCGHSA enrichment
  49. 2026-09-05 15:21 UTCEG score recompute
  50. 2026-09-05 15:21 UTCVendor advisory
  51. 2026-09-05 15:21 UTCGHSA enrichment
  52. 2026-09-05 14:23 UTCEG score recompute
  53. 2026-09-05 14:23 UTCVendor advisory
  54. 2026-09-05 14:23 UTCGHSA enrichment
  55. 2026-09-05 06:53 UTCEG score recompute
  56. 2026-09-05 06:53 UTCVendor advisory
  57. 2026-09-05 06:53 UTCGHSA enrichment
  58. 2026-09-04 12:48 UTCEG score recompute
  59. 2026-09-04 12:48 UTCVendor advisory
  60. 2026-09-04 12:48 UTCGHSA enrichment
  61. 2026-09-04 05:06 UTCEPSS rescore
  62. 2026-09-02 18:41 UTCEG score recompute
  63. 2026-09-02 18:41 UTCVendor advisory
  64. 2026-09-02 18:40 UTCGHSA enrichment
  65. 2026-09-02 14:11 UTCEPSS rescore
  66. 2026-09-01 23:15 UTCEG score recompute
  67. 2026-09-01 23:15 UTCVendor advisory
  68. 2026-09-01 23:15 UTCGHSA enrichment
  69. 2026-09-01 13:53 UTCEPSS rescore
  70. 2026-09-01 04:39 UTCEPSS rescore
  71. 2026-08-30 22:08 UTCEG score recompute
  72. 2026-08-30 22:08 UTCVendor advisory
  73. 2026-08-30 22:08 UTCGHSA enrichment
  74. 2026-08-30 19:17 UTCEPSS rescore
  75. 2026-08-30 11:12 UTCEG score recompute

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, with the most recent update on September 8, 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 71.8% 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