Skip to content

Azure AI Foundry CVSS 10.0 missing-auth privilege escalation

Summary

Microsoft fixed CVE-2026-85889 (CVSS 10.0, Thursday Sep 17 advisory, reported by The Hacker News Sep 18, 2026): "Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network." Azure AI Foundry (a.k.a. Microsoft Foundry) is Microsoft's enterprise platform for building, deploying, and managing generative-AI apps and agents. Found by researcher Rémy Marot (@R_Marot); no in-the-wild exploitation evidence; as with cloud-hosted CVEs, already fully mitigated server-side, no customer action required. The same window brought three more 9.x cloud-side fixes: CVE-2026-85885 (9.9, command injection in Microsoft 365 Copilot, authorized attacker → privilege escalation), CVE-2026-85878 (9.9, improper authorization in Azure Database for PostgreSQL), CVE-2026-87701 (9.6, improper neutralization in Azure Cosmos DB), all pre-mitigated, no customer action. Separately, two Windows out-of-band fixes shipped for Windows 11 26H1 (KB5129194, 28000.2956): CVE-2026-62721 (7.8, insufficient access-control granularity in User-Mode Power Service → local SYSTEM) and CVE-2026-85921 (8.2, double free in Windows Secure Kernel Mode → VTL1 privileges, VSM-side escalation is rare air; the second Secure KM item this month). Context: this follows the record 974-CVE September Patch Tuesday (CrowdStrike's count; the wiki's Patch Tuesday page carried CrowdStrike's 972 figure at analysis time). Durable read: a CVSS 10.0 in the agent-building control plane continues the on-wiki September pattern of maximum-severity flaws landing specifically in AI-platform management layers (Bifrost MCP gateway 9.8, Orkes workflow engine 9.8, AgentCore Harness runtime), not in model runtimes.

Tags

Why this matters

  • AI control planes keep earning maximum scores. Third 9.8-10.0-class flaw this month in a platform whose job is deploying and orchestrating other code (Foundry, Bifrost, Conductor). The privilege-escalation shape at 10.0, missing auth on a critical function reachable over the network, means an unauthenticated caller could gain rights inside the service that governs customer AI workloads. Whether Microsoft-side or tenant-side blast radius, the pattern for defenders is: treat AI-platform management APIs as Tier-1 identity surface, inventory connected grants into them, and monitor Microsoft advisories for Foundry the way you would for Entra.
  • "No customer action required" is a mitigation claim, not a risk claim, log it anyway. Cloud-first CVEs are patched in-place, but the advisory text is the public map of what was broken in services you run. The M365 Copilot command injection at 9.9 (authorized-attacker prerequisite) says Copilot had a path where granted context could reach a command sink: worth watching for a variant reachable from prompt content.
  • Secure Kernel Mode double free → VTL1 (CVE-2026-85921) is the quiet one. Escalation inside Virtual Secure Mode / VSM is the class that defeats Credential Guard-era assumptions; out-of-band 26H1 servicing (KB5129194) says Microsoft treated the 26H1 branch as exposed while servicing caught up. Verify 26H1 arm64/x64 fleets are on 28000.2956+.

Defender actions

  • No Foundry/Copilot/PostgreSQL/Cosmos tenant action per Microsoft, but record the dates if you were running those services before Sep 17: the mitigation window defines when a pre-mitigation intrusion would have been possible.
  • Windows 11 26H1 fleet check: KB5129194 (build 28000.2956) installed? UMPS (CVE-2026-62721) is the kind of local LPE that pairs with browser/office initial access; SKM (CVE-2026-85921) breaks the VTL0→VTL1 assumption.
  • Hunt-shape for the Foundry window (now closed, useful for retro-hunts): unauthenticated calls to Foundry control-plane functions that succeeded (should be zero post-fix), anomalous role assignments on Foundry projects/agents.

Caveats

  • Microsoft did not publicly detail the Foundry function or the escalation's post-conditions; the description is the advisory text verbatim.
  • No ITW evidence for any of the four cloud CVEs; all vendor-mitigated server-side.
  • CrowdStrike's Patch Tuesday tally on-wiki (972) vs THN's "record 974" differs by count methodology; both refer to the same Sep 8 event.

Sources