CVE-2026-58275

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreHIGH confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-24. the CNA's CVSS baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Missing authorization in Azure DNS allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
10.0
EG Score
10.0(high)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

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
Severity100% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

July 24, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

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-58275

Vendor Advisories for CVE-2026-58275(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 96× in last 7d / 130× 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 130 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58275?
CVE-2026-58275 is a critical vulnerability published on July 24, 2026. Missing authorization in Azure DNS allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-58275 disclosed?
CVE-2026-58275 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58275 actively exploited?
CVE-2026-58275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.4% of all scored CVEs.
What is the CVSS score of CVE-2026-58275?
CVE-2026-58275 has a CVSS v4.0 base score of 10.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-58275?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58275, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58275?

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

Start Free Scan →Browse All CVEs