Cyber Resilience

CVE-2025-25006

Microsoft Exchange Server 2016 … 2019

Published
12 August 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0085 55th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2025-25006 is a medium-severity Improper Handling of Additional Special Element (CWE-167) vulnerability in Microsoft Exchange Server. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Improper handling of additional special element in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.

CWE(s)
CWE-167NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-55009Same product: Microsoft Exchange Server
CVE-2026-55008Same product: Microsoft Exchange Server
CVE-2026-45500Same product: Microsoft Exchange Server
CVE-2025-25005Same product: Microsoft Exchange Server
CVE-2026-45501Same product: Microsoft Exchange Server
CVE-2026-55005Same product: Microsoft Exchange Server
CVE-2025-64666Same product: Microsoft Exchange Server
CVE-2026-42897Same product: Microsoft Exchange Server
CVE-2025-59248Same product: Microsoft Exchange Server
CVE-2026-47631Same product: Microsoft Exchange Server

Affected Assets

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

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation partial match

SI-10 requires validity checks on inputs that directly stop additional unexpected special elements from being mishandled.

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
prevents

Secure SDLC practices directly require correct input parsing and special-element handling during development.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches improper handling of unexpected special elements before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and handling of unexpected data elements.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for robust input validation against malformed or special-element data.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include defensive input handling to prevent injection or parsing anomalies.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require correct handling of all input elements, eliminating this weakness.

References