What is the CVSS score of CVE-2026-32211?

CVE-2026-32211 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.1%.

Which versions of Microsoft are affected by CVE-2026-32211?

CVE-2026-32211 is a critical unauthenticated information disclosure vulnerability in Azure MCP Server (CVSS 9.1) that allows remote attackers to extract sensitive data without credentials or…. A patch is available.

How to fix or mitigate CVE-2026-32211?

Within 24 hours: Immediately inventory all Azure MCP Server deployments and document versions; restrict network access to Azure MCP Server instances to trusted networks only using firewall or network segmentation. Within 7 days: Implement network-level controls such as VPN-gating, IP allowlisting, or WAF rules to block unauthenticated access; conduct audit logs for suspicious access patterns. Within 30 days: Monitor Microsoft security advisories for patch availability and apply immediately upon release; evaluate alternative solutions if patch timeline is unacceptable for risk profile.

Microsoft CVE-2026-32211

EUVD-2026-18560 CRITICAL

Missing Authentication for Critical Function (CWE-306)

2026-04-03 secure@microsoft.com

GHSA-5w7p-v6h9-q8c5

Microsoft Authentication Bypass

9.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.1 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Apr 03, 2026 - 00:22 euvd

EUVD-2026-18560

Analysis Generated

Apr 03, 2026 - 00:22 vuln.today

CVE Published

Apr 03, 2026 - 00:16 nvd

CRITICAL 9.1

DescriptionCVE.org

Missing authentication for critical function in Azure MCP Server allows an unauthorized attacker to disclose information over a network.

AnalysisAI

Unauthenticated information disclosure in Azure MCP Server allows remote attackers to access sensitive data over the network without authentication. The vulnerability stems from missing authentication controls on critical functions (CWE-306), enabling attackers to bypass security boundaries and extract confidential information with minimal complexity. With CVSS 9.1 (Critical) and network-accessible attack vector requiring no privileges or user interaction, this represents a significant exposure for organizations running affected Azure MCP Server instances. No public exploit identified at time of analysis, though the straightforward authentication bypass nature increases likelihood of rapid weaponization.

Technical ContextAI

Azure MCP Server is a Microsoft cloud platform component that appears to handle management or control plane operations. The vulnerability is rooted in CWE-306 (Missing Authentication for Critical Function), meaning security-sensitive operations lack proper authentication enforcement at the function or API level. The CVSS vector (AV:N/AC:L/PR:N) indicates the flaw is remotely exploitable over standard network protocols without requiring authentication or complex exploitation techniques. This class of vulnerability typically manifests when developers fail to implement authentication checks on API endpoints, administrative interfaces, or internal service calls that were incorrectly assumed to be protected by perimeter security. The high confidentiality impact (C:H) combined with high integrity impact (I:H) but no availability impact (A:N) suggests attackers can read and potentially modify data but cannot cause service disruption through this specific vulnerability.

RemediationAI

Organizations should immediately consult the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32211 for vendor-supplied patches and specific upgrade instructions. Released patched version details are not included in current intelligence data, so verification through the MSRC portal is essential. As an interim control measure, restrict network access to Azure MCP Server instances using firewall rules, network segmentation, or Azure Network Security Groups to limit exposure to trusted IP ranges until patches can be deployed. Implement enhanced monitoring for unusual authentication patterns or access to sensitive functions. Given the authentication bypass nature, perimeter controls are critical compensating measures while patching is in progress. Priority should be given to internet-facing instances and production environments processing sensitive data.