cve.bz

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

8.1 highEPSS 0.5%

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

On this page
External control of file name or path in .NET allows an unauthorized attacker to elevate privileges over a network.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd 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.
CWEs
CWE-73 External Control of File Name or Path
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-522 Insufficiently Protected Credentials
OWASP Top 10
A01:2025 Broken Access Control, 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-69805 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69805?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69805?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-69805 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-69805

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

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Visual Studio 2022 version 17.14from 17.14.0 before 17.14.40
Microsoft Visual Studio 2026 version 18.9from 18.9.0 before 18.9.3
Microsoft.Diagnostics.Runtimefrom 4.1.740301 before 4.1.740301

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because an unauthorized network-based attacker could achieve elevated privileges within the running application process by manipulating file system paths. Exploitation is constrained by high attack complexity and typically requires user interaction or specific execution contexts to influence path resolution. In standard Red Hat deployments running .NET applications or container images, the blast radius is limited to the privileges granted to the hosting user or container context.

ProductPackageStateAdvisory
Red Hat Hardened Imagesdotnet10.0Not affected
Red Hat Hardened Imagesdotnet8.0Not affected
Red Hat Hardened Imagesdotnet9.0Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-69805.

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. More on the page of CWE-522 (13), CWE-200 (59).

References

Check your stackJSON