Security Resilience

CVE-2026-85878

Access Control in Microsoft Azure Horizondb

Published
18 September 2026
Modified
25 September 2026
Patch / advisory
CVSS Score v3.1 9.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0078 55th percentile
Risk Priority 70 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-85878 is a critical-severity Improper Authorization (CWE-285) vulnerability in Microsoft Azure Horizondb. Its CVSS base score is 9.9 (Critical).

Operationally, ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper authorization in Azure Database for PostgreSQL allows an authorized attacker to elevate privileges over a network.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-30061Same vendor: Microsoft
CVE-2026-48579Same vendor: Microsoft
CVE-2026-42902Same vendor: Microsoft
CVE-2025-59271Same vendor: Microsoft
CVE-2025-21275Same vendor: Microsoft
CVE-2024-26193Same vendor: Microsoft
CVE-2025-30390Same vendor: Microsoft
CVE-2025-53795Same vendor: Microsoft
CVE-2026-54121Same vendor: Microsoft
CVE-2026-59118Same vendor: Microsoft

Affected Assets

microsoft
azure horizondb
all versions

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Mandates that access-control decisions are made and applied to each request before access occurs.

Requires a tamperproof, always-invoked reference monitor that performs authorization checks.

Directly requires enforcement of approved authorizations for every access request, stopping improper or missing checks.

Limits granted privileges so that even a bypassed check affects fewer resources.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.3 directly mandates and configures the authorization mechanisms (identity/group rights, dynamic access rules, isolation, credential enforcement) that stop CWE-285 exploitation; the bounded remainder is non-authorization exposure vectors such as error messages or observable discrepancies.

blocks

Mapping access rights to information classification and business requirements forces correct enforcement of authorization decisions, blocking the incorrect authorization weakness at the policy and implementation stage.

finds

Independent reviewers evaluate whether authorization logic matches policy, thereby reducing the window in which incorrect or missing authorization checks remain in production.

finds

By requiring managers to verify that authorization decisions match policy and to remediate deviations, the control limits the persistence of incorrect or missing authorization checks.

blocks

Mandatory review and acceptance testing of changes before deployment reduces the chance that an authorization decision will be implemented incorrectly or will grant unintended rights.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-285, a class-level weakness. Rules are authored against its narrower children: CWE-552.

References