Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
3DescriptionCVE.org
Improper authorization in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
AnalysisAI
Azure AI Foundry improper authorization permits unauthenticated remote attackers to escalate privileges and achieve complete compromise with high impact to confidentiality, integrity, and availability. The CVSS 10.0 rating reflects network-based attack vector with low complexity, no user interaction, and scope change indicating containerization/isolation escape. EPSS and KEV status not provided, but the authentication bypass affecting a cloud AI platform poses severe risk. No public exploit identified at time of analysis.
Technical ContextAI
This vulnerability stems from CWE-285 (Improper Authorization), indicating flawed access control enforcement in Azure AI Foundry's permission model. Azure AI Foundry is Microsoft's platform for building, deploying, and managing AI applications and models. The authorization defect allows attackers to bypass authentication gates entirely, gaining unauthorized access to privileged operations. The Changed scope (S:C) in the CVSS vector suggests the vulnerability may enable escape from logical boundaries such as tenant isolation or container boundaries within the multi-tenant cloud environment, allowing impact beyond the vulnerable component itself. This class of authorization flaw typically arises from missing or incorrect permission checks in API endpoints, middleware layers, or role-based access control (RBAC) implementations.
RemediationAI
Apply security updates immediately per Microsoft Security Response Center guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32213. Exact patched version numbers were not provided in available intelligence; consult the vendor advisory for deployment-specific update procedures. Given the cloud-managed nature of Azure AI Foundry, Microsoft may deploy server-side fixes automatically, but customers should verify patch application status through Azure portal or service health dashboard. Until confirmation of remediation, implement compensating controls: restrict network access to Azure AI Foundry endpoints using firewall rules or virtual network service endpoints, enable enhanced logging and monitoring for unauthorized privilege escalation attempts, review and audit existing user permissions and API access tokens, and consider temporarily suspending non-critical AI workloads if business continuity allows.
Same weakness CWE-285 – Improper Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-18561
GHSA-ccr7-c63m-8vgm