CVE-2026-32174

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. the CNA's CVSS baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.7Exploit: 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 Bot Service allows an authorized attacker to elevate privileges over a network.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity77% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

June 18, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jun 18, 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-32174

Vendor Advisories for CVE-2026-32174(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 18× in last 7d / 132× 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 312 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32174?
CVE-2026-32174 is a high vulnerability published on June 18, 2026. Improper authentication in Azure Bot Service allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-32174 disclosed?
CVE-2026-32174 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32174 actively exploited?
CVE-2026-32174 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 47.5% of all scored CVEs.
What is the CVSS score of CVE-2026-32174?
CVE-2026-32174 has a CVSS v4.0 base score of 7.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-32174?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32174, 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-32174

Explore →

Is Your Infrastructure Affected by CVE-2026-32174?

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

Start Free Scan →Browse All CVEs