CVE-2026-55006
Microsoft Exchange Server 2016 … 2019
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-55006 is a high-severity Insufficient Granularity of Access Control (CWE-1220) vulnerability in Microsoft Exchange Server. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th percentile by exploit likelihood (below the median); 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-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-44025
Vulnerability Data
Insufficient granularity of access control in Microsoft Exchange Server allows an authorized attacker to elevate privileges locally.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 3 OS baselines
V16.4.2V8.4.2V11.7.1V13.2.4
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Least privilege explicitly demands that only the minimum necessary accesses are granted, eliminating the broad permissions that define this weakness.
AC-24 requires access decisions to be applied precisely and unambiguously to every request, structurally blocking insufficiently granular policies.
AC-3 requires enforcement of authorizations according to policy, directly compelling sufficiently granular rules so broad allowances cannot be introduced.
AC-4 enforces approved information flows with explicit source/destination rules, preventing overly coarse access policies from being deployed.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
PR.IR-01's segmentation + zero-trust rules directly enforce minimum-necessary access at network boundaries, removing most instances of overly broad policy; CWE-1220 can still exist in application-layer or intra-segment controls that this single outcome does not address.
PR.PS-06's general SDLC practices can surface granularity issues during design/review (partial prevention) but do not specifically target access-control policy breadth, so they remove only part of CWE-1220's risk.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.3 mandates configuration mechanisms, per-user/group rights, isolation, and dynamic access management that directly supply the missing granularity for this weakness; well-implemented, the flaw (over-broad policy) stops being present in the product, with only a bounded remainder (e.g. certain physical or non-dynamic edge cases) left over.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
No rule maps to these weaknesses at full or mostly. Tick the option above to see the partial mappings.
Windows Server 2016 (1 partial rule)
- V-225025 Local accounts with blank passwords must be restricted to prevent access from the network. blocks CWE-1220