Authentication Bypass and Privilege Escalation in Azure Bastion
CVE-2025-49752 is a critical vulnerability in Microsoft Azure Bastion that is described as an authentication bypass leading to elevation of privilege. The issue affects the authentication mechanisms of the Azure Bastion service, which is used to broker RDP and SSH access to Azure virtual machines without directly exposing those systems to the internet. Available reporting classifies the weakness as CWE-294, indicating an authentication bypass scenario consistent with replay or reuse of authentication material. Successful remote exploitation could allow an unauthenticated attacker to obtain administrative-level privileges through the Bastion service. Publicly available information does not disclose the precise root cause, vulnerable code path, or protocol element involved.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation could allow a remote attacker to bypass authentication in Azure Bastion and escalate privileges to an administrative level within the service context. Because Azure Bastion commonly serves as the managed access plane for multiple Azure virtual machines, compromise of the Bastion service could expose all VMs reachable through that Bastion deployment to unauthorized administrative access. This creates risk of broad tenant impact, including unauthorized remote access to systems, follow-on compromise of hosted workloads, and loss of confidentiality, integrity, and availability across connected virtual machine environments.
If you can’t patch tonight, do this now.
Follow Microsoft's published guidance for Azure Bastion associated with the 2025-11-20 security release, including any service-side mitigations or workarounds the vendor provides. Where immediate remediation cannot be confirmed, reduce reliance on affected Bastion instances for privileged administration, restrict administrative access paths to the minimum necessary, closely monitor Bastion-mediated session activity, and review access to virtual machines reachable through the service for signs of unauthorized use.
Patch, then assume compromise.
Apply Microsoft's security updates for Azure Bastion released on 2025-11-20. Available reporting indicates that deployments prior to that security update are potentially affected. Organizations should ensure their Azure Bastion instances are updated to the vendor-remediated service state and validate through Microsoft guidance that the fix has been fully applied across all affected environments.
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.