cve.bz

CVE-2026-69355 microsoft: External Control of File Name or Path

8.8 highEPSS 0.9%Fix available

High (8.8) in microsoft. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 61st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-73 External Control of File Name or Path
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-69355 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69355?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69355?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-69355 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-69355

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-69355](https://cve.bz/cve/badge/CVE-2026-69355.svg)](https://cve.bz/cve/CVE-2026-69355)

HTML:

<a href="https://cve.bz/cve/CVE-2026-69355"><img src="https://cve.bz/cve/badge/CVE-2026-69355.svg" alt="CVE-2026-69355"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Exchange Server 2016 Cumulative Update 23from 15.01.0.0 before 15.01.2507.073
Microsoft Exchange Server 2019 Cumulative Update 14from 15.02.0.0 before 15.02.1544.046
Microsoft Exchange Server 2019 Cumulative Update 15from 15.02.0.0 before 15.02.1748.051
Microsoft Exchange Server Subscription Edition RTMfrom 15.02.0.0 before 15.02.2562.049

Attack patterns (CAPEC)

  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON