CVE-2026-62825

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.

Improper authentication in Azure Key Vault 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-62825

Vendor Advisories for CVE-2026-62825(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 90× in last 7d / 95× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-62825?
CVE-2026-62825 is a critical vulnerability published on July 24, 2026. Improper authentication in Azure Key Vault allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-62825 disclosed?
CVE-2026-62825 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-62825 actively exploited?
CVE-2026-62825 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 50.6% of all scored CVEs.
What is the CVSS score of CVE-2026-62825?
CVE-2026-62825 has a CVSS v4.0 base score of 10.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62825?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62825, 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-62825

Explore →

Is Your Infrastructure Affected by CVE-2026-62825?

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

Start Free Scan →Browse All CVEs