Security Resilience

CVE-2026-21527

Microsoft Exchange Server 2016 … 2019

Published
10 February 2026
Modified
15 June 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.083 95th percentile
Risk Priority 60 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-21527 is a medium-severity Insufficient Verification of Data Authenticity (CWE-345) vulnerability in Microsoft Exchange Server. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Compression (T1027.015); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

User interface (ui) misrepresentation of critical information in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1027.015 Compression Stealth
Adversaries may use compression to obfuscate their payloads or files.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-25007Same product: Microsoft Exchange Server
CVE-2025-64667Same product: Microsoft Exchange Server
CVE-2026-45501Same product: Microsoft Exchange Server
CVE-2026-45503Same product: Microsoft Exchange Server
CVE-2026-65813Same product: Microsoft Exchange Server
CVE-2026-45502Same product: Microsoft Exchange Server
CVE-2026-45504Same product: Microsoft Exchange Server
CVE-2025-25006Same product: Microsoft Exchange Server
CVE-2026-69355Same product: Microsoft Exchange Server
CVE-2026-55009Same product: Microsoft Exchange Server

Affected Assets

microsoft
exchange server
2016, 2019
microsoft
exchange server subscription edition
≤ 15.02.2562.037

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.2
  • V2.2.2
  • V3.5.5
  • V5.4.1

Mitigating Controls (NIST 800-53 r5) AI

Explicit requirement to protect session authenticity structurally prevents the weakness for communications.

SI-10 requires validation of information inputs for correctness, directly stopping syntactic validation failures from being introduced or exploitable.

Integrity verification tools detect (but do not stop) the acceptance of data lacking authenticity.

Cryptographic mechanisms can be used to verify authenticity, thereby preventing acceptance of invalid data.

Associating security attributes with exchanged information supports verification of authenticity.

Integrity protection on transmitted data directly stops acceptance of unauthenticated or altered data.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require syntactic input validation to prevent malformed data handling.

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.

finds

Security testing can detect missing or weak data authenticity verification.

blocks

A.8.24's guidance on identifying protection levels, selecting algorithms/strength for authenticity/integrity (items b,f), using cryptography for transmitted/stored data (c), and key management directly stops many CWE-345 exploits by ensuring verifiable authenticity; however, it leaves a bounded remainder where verification logic itself is flawed or absent (e.g. accepting unverified signatures or weak schemes), as the control depends on correct implementation in other mechanisms.

prevents

Secure coding practices include implementing proper data authenticity checks.

blocks

Secure authentication of data sources ensures only valid, authentic data is accepted.

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-345, a class-level weakness. Rules are authored against its narrower children: CWE-347, CWE-348, CWE-349, CWE-353, CWE-354, CWE-494, CWE-649, CWE-924.
  • No fine-grained STIG row for CWE-451, a class-level weakness, and none of its children carries one either.

References