CVE-2026-73267

HIGHPre-NVD 7.77.7
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

A flaw was found in the clusterclaims-controller component of multicluster engine (MCE). A tenant with standard permissions to create and delete ClusterClaim resources can exploit this by manipulating the spec.namespace field. This allows the tenant to specify and delete any ManagedCluster, including the hub's local-cluster or other tenants' clusters, due to a missing ownership check. This vulnerability can lead to a denial of service by enabling unauthorized deletion of ManagedClusters.

CVSS v3
7.7
EG Score
7.7(high)
EG Risk
35(Track)
EG Risk 35/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
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

August 21, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Aug 21, 2026
Patch available. Sources: redhat.
redhat

2514218 – (CVE-2026-73267) CVE-2026-73267 clusterclaims-controller: clusterclaims-controller: ManagedCluster deletion keyed solely on ClusterClaim.Spec.Namespace with no ownership check

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

CVE-2026-73267 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

Patch Availability(6)

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 35× in last 7d / 183× 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 183 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73267?
CVE-2026-73267 is a high vulnerability published on August 21, 2026. A flaw was found in the clusterclaims-controller component of multicluster engine (MCE). A tenant with standard permissions to create and delete ClusterClaim resources can exploit this by manipulating the spec.namespace field. This allows the tenant to specify and delete any ManagedCluster,…
When was CVE-2026-73267 disclosed?
CVE-2026-73267 was first published in the National Vulnerability Database on August 21, 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-73267 actively exploited?
CVE-2026-73267 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 60.7% of all scored CVEs.
What is the CVSS score of CVE-2026-73267?
CVE-2026-73267 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-73267?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73267, 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-73267

Explore →

Is Your Infrastructure Affected by CVE-2026-73267?

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