Cyber Resilience

CVE-2026-62910

Microsoft Exchange Server 2016 … 2019

Published
11 August 2026
Modified
14 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0068 49th percentile
Risk Priority 54 floored blend · peak EPSS

Summary

CVE-2026-62910 is a high-severity Resource Injection (CWE-99) vulnerability in Microsoft Exchange Server. Its CVSS base score is 7.2 (High).

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

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Improper control of resource identifiers ('resource injection') in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.

CWE(s)
CWE-99

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 →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
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-45504Same product: Microsoft Exchange Server
CVE-2025-25007Same product: Microsoft Exchange Server
CVE-2026-45502Same product: Microsoft Exchange Server
CVE-2026-62913Same product: Microsoft Exchange Server
CVE-2026-55005Same product: Microsoft Exchange Server
CVE-2025-64666Same product: Microsoft Exchange Server
CVE-2025-25005Same product: Microsoft Exchange Server
CVE-2025-59248Same product: Microsoft Exchange Server
CVE-2025-53782Same product: Microsoft Exchange Server

Affected Assets

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

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.3.8
  • V1.3.9
  • V1.3.11
  • V9.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Directly requires validation of inputs before they are accepted as resource identifiers.

AC-3 Access Enforcement partial match

Enforces authorizations on resource access so an injected identifier cannot reach outside the intended sphere.

AC-4 Information Flow Enforcement partial match

Enforces information flow rules that block use of untrusted identifiers to reach unauthorized resources.

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 input validation and sanitization that prevent resource-identifier injection flaws.

PR.AA-05 partial match
prevents

Least-privilege access policy and enforcement limits damage from injected resource identifiers even when input validation is absent.

PR.IR-01 partial match
prevents

Network segmentation and unauthorized-access controls reduce the blast radius of successful resource injection.

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 can detect resource-injection flaws but does not itself implement preventive controls.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and resource-identifier sanitization that directly prevents resource injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls on external identifiers used to access resources.

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

Secure architecture principles reduce attack surface for resource injection but do not prescribe identifier validation.

A.8.28 Secure coding partial match
prevents

Secure coding standards require strict validation and whitelisting of all resource identifiers before use.

A.8.3 Information access restriction partial match
mitigates

Information-access-restriction policies limit which resources can be referenced, indirectly reducing injection impact.

References