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: 0%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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

June 18, 2026

Last Modified

July 28, 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 27× in last 7d / 116× 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 182 total refreshes for this CVE.

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

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 July 28, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 66.3% 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