# Azure Database for PostgreSQL Elevation of Privilege Vulnerability

CVE record · `CVE-2026-85878`

- **Identifiers:** `CVE-2026-85878`
- **State:** Confirmed
- **Severity:** CVSS 9.9 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** microsoft
- **Weakness (CWE):** [CWE-285](https://cwe.mitre.org/data/definitions/285.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Technologies:** [Microsoft Azure HorizonDB](https://agentprime.io/advisories/technology/microsoft-azure-horizondb.md)
- **Published:** 17 Sept 2026
- **Updated:** 10 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: microsoft) at 17 Sept 2026, 23:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 9.9: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: Microsoft. Product: Azure HorizonDB.
  - affected: `-`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Microsoft Azure HorizonDB is affected by an improper authorization flaw, described in the source as part of Azure Database for PostgreSQL; the source does not list affected version numbers. An attacker who already has an authorized account can exploit it over a network to elevate their privileges. The source gives few further details, and no fix is listed.

Written 11 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 9.9 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C`, from CNA (microsoft)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0078, the 56th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 17 Sept 2026, 23:04 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-85878)
- 31 Oct 2026, 16:26 UTC: First seen by agentprime

## Sources

- [CVE List: CVE-2026-85878](https://www.cve.org/CVERecord?id=CVE-2026-85878)
- [NVD: CVE-2026-85878](https://nvd.nist.gov/vuln/detail/CVE-2026-85878)

### References from the CNA

- <https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85878> (vendor-advisory, patch)

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-85878>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-85878/>. Everything for agents: <https://agentprime.io/llms.txt>.