cve.bz

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

4.3 mediumEPSS 0.6%

Medium (4.3) in microsoft. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
Files or directories accessible to external parties in Microsoft Office Word allows an unauthorized attacker to disclose information locally.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th 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: partial, assessed 2026-05-13. 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
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40421 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40421?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40421?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-40421 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-40421

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-40421](https://cve.bz/cve/badge/CVE-2026-40421.svg)](https://cve.bz/cve/CVE-2026-40421)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft 365 Apps for Enterprisefrom 16.0.1 before https://aka.ms/OfficeSecurityReleases
Microsoft Office 2019from 19.0.0 before https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC 2021from 16.0.1 before https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC 2024from 16.0.0 before https://aka.ms/OfficeSecurityReleases
Microsoft Word 2016from 16.0.1 before 16.0.5552.1000

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