CVE-2026-23662

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-10. The CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Missing authentication for critical function in Azure IoT Explorer allows an unauthorized attacker to disclose information over a network.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

March 10, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated Jun 23, 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-23662

Vendor Advisories for CVE-2026-23662(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 28× 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 99 of 170 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 71 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-23662?
CVE-2026-23662 is a high-severity vulnerability; its CVE record was published on March 10, 2026. Missing authentication for critical function in Azure IoT Explorer allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-23662 made public?
CVE-2026-23662 was made public on March 10, 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 March 10, 2026. EchelonGraph's copy of the record carries a last-modified date of June 19, 2026; the record at its source may have been updated since.
Is CVE-2026-23662 actively exploited?
CVE-2026-23662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23662?
CVE-2026-23662 has a CVSS base score of 7.5 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-23662?
A fix for CVE-2026-23662 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23662 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-23662?

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

Book a Demo →Browse All CVEs