CVE-2026-23664

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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: cna:microsoft, epss, ghsa
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Improper restriction of communication channel to intended endpoints 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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.0%
EPSS %ILE
62nd
KEV
Not listed

Published

March 10, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
microsoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

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

Vendor Advisories for CVE-2026-23664(1)

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 6× in last 7d / 22× 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 161 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23664?
CVE-2026-23664 is a high vulnerability published on March 10, 2026. Improper restriction of communication channel to intended endpoints in Azure IoT Explorer allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-23664 disclosed?
CVE-2026-23664 was first published on March 10, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23664 actively exploited?
CVE-2026-23664 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23664?
CVE-2026-23664 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-23664?
A fix for CVE-2026-23664 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-23664 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-23664?

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