CVE-2026-54100

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

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

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-22. A secondary CVSS source baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week
8.3EG
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.3%CVSS: 8.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in the Windows Machine Config Operator (WMCO) for Red Hat OpenShift Container Platform. WMCO establishes SSH connections to Windows worker nodes without verifying the remote server host key. An adjacent-network attacker who can intercept or redirect WMCO's SSH session can capture WICD and kubelet bootstrap credentials transferred during node configuration, enabling compromise of Windows node identities in the cluster.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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 (value × EchelonGraph’s weight)
Severity83% × 45%
The EG Score, 8.3 of 10.
Exploitation0.3% × 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.3%
EPSS %ILE
21st
KEV
Not listed

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.

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

June 22, 2026

Last Modified

October 14, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat.
Red Hat

2487953 – (CVE-2026-54100) CVE-2026-54100 windows-machine-config-operator: windows-machine-config-operator: SSH host key not verified enables credential theft

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

cve-details

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

Patch Availability(3)

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 20× in last 7d / 41× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 361 refreshes 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 261 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-54100?
CVE-2026-54100 is a high-severity vulnerability; its CVE record was published on June 22, 2026. A flaw was found in the Windows Machine Config Operator (WMCO) for Red Hat OpenShift Container Platform. WMCO establishes SSH connections to Windows worker nodes without verifying the remote server host key. An adjacent-network attacker who can intercept or redirect WMCO's SSH session can capture…
When was CVE-2026-54100 made public?
CVE-2026-54100 was made public on June 10, 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 June 22, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-54100 actively exploited?
CVE-2026-54100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54100?
CVE-2026-54100 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54100?
A fix for CVE-2026-54100 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54100 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54100?

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