EUVD-2026-37945
GHSA-qv5v-67pv-5jmc
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable managed service (AV:N/AC:L) requiring an existing low-privilege authenticated foothold (PR:L) to elevate; no user interaction; high C/I/A consistent with privilege gain over bot resources.
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
6DescriptionNVD
Improper authentication in Azure Bot Service allows an authorized attacker to elevate privileges over a network.
AnalysisAI
Privilege elevation in Microsoft's Azure (AI) Bot Service lets an authenticated, network-based attacker bypass improper authentication checks (CWE-287) to gain higher privileges than originally granted. Tracked as CVE-2026-32174 (CVSS 8.8) and reported by Microsoft, it affects the cloud-hosted Azure Bot Service and carries high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis, EPSS exploitation probability is low (0.37%, 29th percentile), and CISA SSVC currently scores exploitation as 'none.'
Technical ContextAI
Azure Bot Service (CPE cpe:2.3:a:microsoft:azure_ai_bot_service) is Microsoft's managed cloud platform for building, hosting, and connecting conversational bots across channels (Teams, Web Chat, Direct Line, etc.), with authentication typically brokered through Azure AD/Entra identities and channel tokens. The root cause is CWE-287 (Improper Authentication): the service fails to correctly validate or enforce the identity/authorization context of a request, allowing a caller who already holds some legitimate access (PR:L) to be treated as more privileged than intended. Because this is a multi-tenant managed service, the flaw resides in Microsoft's backend authentication logic rather than in customer-deployed software versions.
RemediationAI
Patch available per vendor advisory: Microsoft reports a fix is available, and because Azure Bot Service is a managed cloud service the remediation is applied server-side by Microsoft, so most customers require no manual update - confirm exposure and any required client/SDK or channel reconfiguration via the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32174. No exact fix version is published (none applies to the hosted service). As compensating measures pending or alongside Microsoft's fix, tighten the bot's authentication posture: enforce least-privilege Azure AD/Entra roles for bot identities and connected app registrations, rotate Direct Line/channel secrets and bot app passwords, restrict which channels and Direct Line sites are enabled (disable unused channels to reduce reachable surface), and review sign-in and resource access logs for anomalous privilege use. These controls reduce the value of any stolen low-privilege foothold but do not substitute for Microsoft's backend fix; over-restricting channels or rotating secrets without coordination can disrupt live bot connectivity.
More in Azure Ai Bot Service
View allImproper authorization in Azure Bot Framework SDK allows an unauthorized attacker to elevate privileges over a network.
Improper authorization in Azure Bot Framework SDK allows an unauthorized attacker to elevate privileges over a network.
Azure Bot Service Elevation of Privilege Vulnerability. Rated critical severity (CVSS 9.0), this vulnerability is remote
Same weakness CWE-287 – Improper Authentication
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today