Skip to main content
CVE-2025-49752VulnerabilityPublished Updated

CVE-2025-49752: Microsoft Azure Bastion Developer · Authentication Bypass by Capture-replay

Affects Microsoft Azure Bastion DeveloperSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Immediately restrict network access to Azure Bastion Developer instances using network security groups (NSGs) or firewall rules to limit exposure to trusted IP addresses only. 2. Monitor network traffic for unusual or repeated authentication attempts that could indicate capture-replay attacks, using Azure Monitor and Azure Sentinel for anomaly detection. 3. Implement multi-factor authentication (MFA) and conditional access policies for Azure portal and management interfaces to reduce risk of compromised credentials being leveraged. 4. Isolate critical virtual machines and sensitive workloads behind additional layers of network segmentation and zero trust controls to limit lateral movement if compromise occurs. 5. Stay informed through Microsoft security advisories and apply patches or updates immediately once released. 6. Conduct regular security assessments and penetration testing focusing on Azure Bastion configurations and access controls. 7. Educate security teams about this vulnerability and prepare incident response plans specific to cloud authentication bypass scenarios. 8. Consider temporary alternative secure remote access methods if feasible until the vulnerability is patched.

Description

Azure Bastion Elevation of Privilege Vulnerability

References

Community reviews

Loading reviews…