Cyber Resilience

CVE-2026-69355

Path Traversal in Microsoft Exchange Server 2016 … 2019

Published
08 September 2026
Modified
30 September 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0091 59th percentile
Risk Priority 66 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-69355 is a high-severity External Control of File Name or Path (CWE-73) vulnerability in Microsoft Exchange Server. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 41% 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) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

External control of file name or path in Microsoft Exchange Server allows an authorized attacker to execute code over a network.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
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.
T1574.006 Dynamic Linker Hijacking Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables the dynamic linker uses to load shared libraries.
T1574.007 Path Interception by PATH Environment Variable Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-26360Shared CWE-73
CVE-2025-13320Shared CWE-73
CVE-2024-12058Shared CWE-73
CVE-2025-48067Shared CWE-73
CVE-2025-0124Shared CWE-73
CVE-2026-73619Shared CWE-73
CVE-2025-29930Shared CWE-73
CVE-2023-2554Shared CWE-73
CVE-2025-10494Shared CWE-73
CVE-2026-26157Shared CWE-73

Affected Assets

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

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)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly rejects or sanitizes untrusted path strings before they reach filesystem operations.

Enforces authorization checks on the actual resource accessed, blocking unauthorized files even when a malicious path is supplied.

Least-privilege limits the set of files or directories any subject can affect, shrinking the blast radius of a path-control flaw.

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.AA-05 partial match
prevents

Least-privilege file authorization directly limits damage from externally controlled paths.

PR.PS-06 partial match
prevents

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

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.

prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent external file/path manipulation.

prevents

Application security requirements explicitly call for controls against untrusted input influencing file operations.

prevents

Secure architecture principles discourage unsafe path construction but do not prescribe concrete file-name controls.

prevents

Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.

finds

Security testing can detect path-traversal issues but does not itself implement preventive controls.

References