dbcve.org
Azure Ai FoundryApplication · Microsoft

CVE-2026-32213

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper authorization in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an authorization vulnerability in Azure AI Foundry where the service fails to properly validate user permissions, allowing an unauthenticated attacker to escalate privileges over the network. The improper authorization check enables attackers to gain higher-level access than what their account should permit.

MitigationMonitor for Microsoft's security updates to Azure AI Foundry and apply any provided patches or configuration changes immediately. Review access controls and audit privileged user accounts as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure Ai FoundryApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Azure AI Foundry deployment
    Check your Azure subscription for deployed Azure AI Foundry resources using Azure Portal, Azure CLI ('az resource list --resource-type Microsoft.AI/foundries'), or Azure Resource Graph
    Affected if No Azure AI Foundry resources are deployed - not affected. If resources exist, proceed to next checks.
  2. Verify network exposure
    Review the network configuration of your Azure AI Foundry endpoints. Check if public network access is enabled or if the service is exposed to the internet using Azure Network Security Group rules or Azure Firewall logs
    Affected if The service is publicly accessible over the internet without proper network restrictions - potential attack surface exists.
  3. Examine role-based access control (RBAC) assignments
    List all role assignments for the Azure AI Foundry resource using Azure Portal under 'Access control (IAM)' or Azure CLI ('az role assignment list --scope <resource-id>')
    Affected if Unexpected or overly permissive role assignments exist (e.g., users granted Owner/Contributor roles without justification), or assignments to unfamiliar principals are present.
  4. Review Azure Activity Log for authorization anomalies
    Query Azure Activity Log for events related to your Azure AI Foundry resource. Filter for operation names containing 'authorization' or failed permission checks, and look for operations occurring from unexpected IP addresses or outside normal business hours
    Affected if Audit logs show failed authorization checks, privilege escalation attempts, or operations performed by users with insufficient permissions.
  5. Check for Microsoft security advisories
    Monitor the Microsoft Security Response Center (msrc.microsoft.com) and Azure service health advisories for any published guidance specific to CVE-2026-32213
    Affected if Microsoft has released a security update or advisory indicating the vulnerability applies to your deployment configuration.

If Azure AI Foundry is deployed, exposed to network access, and exhibits any authorization anomalies or unexpected role assignments, the environment may be affected by this privilege escalation vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Monitor for Microsoft's security updates to Azure AI Foundry and apply any provided patches or configuration changes immediately. Review access controls and audit privileged user accounts as a precautionary measure.

Fix this in Azure Ai Foundry Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32213 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data