# CVE-2025-49752: Azure Bastion Elevation of Privilege Vulnerability

> Attackers can escalate privileges within Azure Bastion, potentially gaining unauthorized access to higher-level resources.

- **Severity:** Critical 10.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-5pwg-wh3j-76j8

## What is CVE-2025-49752?

CVE-2025-49752 is a critical vulnerability in Microsoft Azure Bastion Developer, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Azure Bastion Elevation of Privilege Vulnerability

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2025-49752?

It affects 1 product.


Products: Microsoft Azure Bastion Developer.

## How do I fix CVE-2025-49752?

No fix has been published for CVE-2025-49752 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-49752 being exploited?

There is no known exploitation of CVE-2025-49752 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49752 and fix it if it is affected.

What it is: CVE-2025-49752 is a critical vulnerability in Microsoft Azure Bastion Developer, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-49752 in the wild and no public exploit code.

Affected product: Microsoft Azure Bastion Developer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49752/ (Markdown: https://insights.sbomify.com/CVE-2025-49752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49752
- OSV: https://osv.dev/vulnerability/CVE-2025-49752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49752/
Summaries are generated and may contain mistakes; the official description above is the record.