CVE-2026-58289

CRITICALNVD 8.39.0
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-03. NVD baseline CVSS 8.3; sources differ by 0.7.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-41586 (ENISA EUVD) · GHSA-39f3-ggrp-rph3 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 2.0%CVSS: 8.3Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.

CVSS v3
8.3
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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
2.0%
EPSS %ILE
80th
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.0% 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

July 3, 2026

Last Modified

November 10, 2026

Advisory Details (1)

Auto-updated Jul 6, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58289

Vendor Advisories for CVE-2026-58289(2)

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 17× in last 7d / 81× 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 811 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 711 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-52632
    Published Aug 10, 2026

    Microsoft Edge 150.0.4078.48 - RCE

    Open source ↗

Frequently asked(5)

What is CVE-2026-58289?
CVE-2026-58289 is a critical-severity vulnerability; its CVE record was published on July 3, 2026. Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
When was CVE-2026-58289 made public?
CVE-2026-58289 was made public on July 3, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 3, 2026. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-58289 actively exploited?
CVE-2026-58289 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58289?
CVE-2026-58289 has a CVSS v3 base score of 8.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2026-58289?
A fix for CVE-2026-58289 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58289 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58289?

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