CVE-2026-72526

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-12. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-57057 (ENISA EUVD) · GHSA-hp26-rmxw-4cpv (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in the multicloud-integrations component. The Application propagation controller processes the ocm-managed-cluster annotation from an Application Custom Resource (CR) without proper validation. A tenant with permissions to create Applications on the hub cluster can exploit this to target arbitrary managed clusters. This can force ArgoCD on the spoke clusters to synchronize attacker-controlled manifests, leading to arbitrary code execution or privilege escalation on those clusters.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 12, 2026

Last Modified

October 24, 2026

Advisory Details (8)

Auto-updated Nov 9, 2026
Patch available. Sources: redhat.
Red Hat

2514227 – (CVE-2026-72526) CVE-2026-72526 multicloud-integrations: multicloud-integrations: pull-model propagation allows hub tenant to target arbitrary spoke cluster via unvalidated ocm-managed-cluster annotation

https://bugzilla.redhat.com/show_bug.cgi?id=2514227
Red HatMentions a patch (unverified)

CVE-2026-72526 - 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-72526
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60391
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60390
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60389
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60388
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60387
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60386

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhacm2/multicloud-integrations-rhel9:17872521792026-08-26redhat
redhatrhacm2/multicloud-integrations-rhel9:17872432212026-08-26redhat
redhatrhacm2/multicloud-integrations-rhel9:17872591062026-08-26redhat
redhatrhacm2/multicloud-integrations-rhel9:17872386042026-08-26redhat
redhatrhacm2/multicloud-integrations-rhel9:17871834072026-08-26redhat
redhatrhacm2/multicloud-integrations-rhel9:17872606892026-08-26redhat

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 19× in last 7d / 84× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 686 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 586 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-13 05:02 UTCEchelonGraph re-scored
  3. 2026-11-13 05:02 UTCVendor advisory
  4. 2026-11-13 05:02 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  5. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-12 03:11 UTCEchelonGraph re-scored
  7. 2026-11-12 03:11 UTCVendor advisory
  8. 2026-11-12 03:11 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  9. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-11 01:19 UTCEchelonGraph re-scored
  11. 2026-11-11 01:19 UTCVendor advisory
  12. 2026-11-11 01:19 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-11-09 23:25 UTCEchelonGraph re-scored
  15. 2026-11-09 23:25 UTCVendor advisory
  16. 2026-11-09 23:25 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  17. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-11-08 21:34 UTCEchelonGraph re-scored
  19. 2026-11-08 21:34 UTCVendor advisory
  20. 2026-11-08 21:34 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  21. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-11-07 19:42 UTCEchelonGraph re-scored
  23. 2026-11-07 19:42 UTCVendor advisory
  24. 2026-11-07 19:42 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  25. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 75 more
  1. 2026-11-06 17:51 UTCEchelonGraph re-scored
  2. 2026-11-06 17:51 UTCVendor advisory
  3. 2026-11-06 17:51 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-05 15:59 UTCEchelonGraph re-scored
  7. 2026-11-05 15:59 UTCVendor advisory
  8. 2026-11-05 15:59 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  9. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-04 14:07 UTCEchelonGraph re-scored
  11. 2026-11-04 14:07 UTCVendor advisory
  12. 2026-11-04 14:07 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-11-03 12:14 UTCEchelonGraph re-scored
  15. 2026-11-03 12:14 UTCVendor advisory
  16. 2026-11-03 12:14 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  17. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-11-02 10:22 UTCEchelonGraph re-scored
  19. 2026-11-02 10:22 UTCVendor advisory
  20. 2026-11-02 10:22 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  21. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-11-01 08:26 UTCEchelonGraph re-scored
  23. 2026-11-01 08:26 UTCVendor advisory
  24. 2026-11-01 08:26 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  25. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  26. 2026-10-31 06:34 UTCEchelonGraph re-scored
  27. 2026-10-31 06:34 UTCVendor advisory
  28. 2026-10-31 06:34 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  29. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-10-30 04:43 UTCEchelonGraph re-scored
  31. 2026-10-30 04:43 UTCVendor advisory
  32. 2026-10-30 04:43 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  33. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  34. 2026-10-29 02:51 UTCEchelonGraph re-scored
  35. 2026-10-29 02:51 UTCVendor advisory
  36. 2026-10-29 02:51 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  37. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  38. 2026-10-28 00:58 UTCEchelonGraph re-scored
  39. 2026-10-28 00:58 UTCVendor advisory
  40. 2026-10-28 00:58 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  41. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  42. 2026-10-26 23:04 UTCEchelonGraph re-scored
  43. 2026-10-26 23:04 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  44. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  45. 2026-10-25 17:50 UTCEchelonGraph re-scored
  46. 2026-10-25 17:50 UTCVendor advisory
  47. 2026-10-25 17:50 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  48. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  49. 2026-10-25 14:06 UTCEchelonGraph re-scored
  50. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  51. 2026-10-24 15:26 UTCVendor advisory
  52. 2026-10-24 15:26 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  53. 2026-10-23 20:27 UTCEchelonGraph re-scored
  54. 2026-10-23 20:27 UTCVendor advisory
  55. 2026-10-23 20:27 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  56. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  57. 2026-10-23 06:02 UTCEchelonGraph re-scored
  58. 2026-10-23 06:02 UTCVendor advisory
  59. 2026-10-23 06:02 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  60. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  61. 2026-10-22 04:10 UTCEchelonGraph re-scored
  62. 2026-10-22 04:10 UTCVendor advisory
  63. 2026-10-22 04:10 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  64. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  65. 2026-10-21 02:15 UTCEchelonGraph re-scored
  66. 2026-10-21 02:15 UTCVendor advisory
  67. 2026-10-21 02:14 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  68. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  69. 2026-10-20 00:23 UTCEchelonGraph re-scored
  70. 2026-10-20 00:23 UTCVendor advisory
  71. 2026-10-20 00:22 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9
  72. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  73. 2026-10-18 22:26 UTCEchelonGraph re-scored
  74. 2026-10-18 22:26 UTCVendor advisory
  75. 2026-10-18 22:26 UTCGHSA enrichmentGHSA-hp26-rmxw-4cpv · GitHub severity CRITICAL · GitHub CVSS 9.9

Frequently asked(5)

What is CVE-2026-72526?
CVE-2026-72526 is a critical-severity vulnerability; its CVE record was published on August 12, 2026. A flaw was found in the multicloud-integrations component. The Application propagation controller processes the ocm-managed-cluster annotation from an Application Custom Resource (CR) without proper validation. A tenant with permissions to create Applications on the hub cluster can exploit this to…
When was CVE-2026-72526 made public?
CVE-2026-72526 was made public on August 11, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 12, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-72526 actively exploited?
CVE-2026-72526 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72526?
CVE-2026-72526 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72526?
A fix for CVE-2026-72526 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72526 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-72526?

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