# CVE-2025-29813: Azure DevOps Elevation of Privilege Vulnerability

> An authentication bypass in Azure DevOps allows unauthorized attackers to elevate privileges over the network.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/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:** 8 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-jhcc-gwm2-46v7

## What is CVE-2025-29813?

CVE-2025-29813 is a critical authentication bypass vulnerability in Microsoft Azure DevOps, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass by assumed-immutable data in Azure DevOps allows an unauthorized attacker to elevate privileges over a network.

Weakness: CWE-287 (Improper Authentication), CWE-302 (Authentication Bypass by Assumed-Immutable Data)

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

It affects 1 product.


Products: Microsoft Azure Devops.

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

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

## Is CVE-2025-29813 being exploited?

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

## Other vulnerabilities in Microsoft Azure DevOps

- [CVE-2026-42826](https://insights.sbomify.com/CVE-2026-42826/): Azure DevOps Information Disclosure Vulnerability (critical 10.0)
- [CVE-2025-47158](https://insights.sbomify.com/CVE-2025-47158/): Azure DevOps Server Elevation of Privilege Vulnerability (critical 9.0)
- [CVE-2026-23658](https://insights.sbomify.com/CVE-2026-23658/): Azure DevOps: msazure Elevation of Privilege Vulnerability (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29813 is a critical authentication bypass vulnerability in Microsoft Azure DevOps, published on 8 May 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-29813 in the wild and no public exploit code.

Affected product: Microsoft Azure DevOps. 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-29813/ (Markdown: https://insights.sbomify.com/CVE-2025-29813/index.md)
```

## Sources

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

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