Skip to main content
Mallory
CriticalVulnerability

CVE-2025-49752: Authentication Bypass and Privilege Escalation in Azure Bastion

Published Nov 20, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v3.1
EPSS0.91%61st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2025-49752CWE-294 · Authentication Bypass by…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationAzure Bastion Developerapplication
FAQ

Frequently asked questions

Is CVE-2025-49752 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-49752 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-49752?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-49752.
Is there a patch for CVE-2025-49752?
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.
What products are affected by CVE-2025-49752?
Microsoft Corporation Azure Bastion Developer.
How severe is CVE-2025-49752?
CVE-2025-49752 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 0.91% (61st percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity13Community discussion across Reddit, Mastodon, and other social sources.