CVE-2026-69805: External control of file name or path in .NET allows an unauthorized attacker to elevate privileges over a net

This month

HIGH 7.5WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-69805 is a high-severity flaw (CVSS 7.5) affecting microsoft.diagnostics.runtime, visual studio 2022, visual studio 2026. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-73, CWE-200, CWE-522
Published	2026-09-08
Last modified	2026-09-29

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-09-29 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-08 18:19 UTCPublished CVE record published
2026-09-29 19:54 UTCUpdated Record last modified

microsoft microsoft.diagnostics.runtime UPGRADE

Affected: < 4.1.740301

Fixed in: 4.1.740301

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy microsoft.diagnostics.runtime || rpm -q microsoft.diagnostics.runtime || microsoft.diagnostics.runtime --version

2. UPGRADE to 4.1.740301 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade microsoft.diagnostics.runtime

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade microsoft.diagnostics.runtime

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

microsoft visual studio 2022 UPGRADE

Affected: >= 17.14.0 and < 17.14.40

Fixed in: 17.14.40

Safe to downgrade to: a release before 17.14.0

1. Check installed version

apt-cache policy visual-studio-2022 || rpm -q visual-studio-2022 || visual-studio-2022 --version

2. UPGRADE to 17.14.40 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade visual-studio-2022

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade visual-studio-2022

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 17.14.0 (Debian / Ubuntu)

apt-cache madison visual-studio-2022 sudo apt install visual-studio-2022=<VERSION_BEFORE_17.14.0> sudo apt-mark hold visual-studio-2022

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list visual-studio-2022 sudo dnf downgrade visual-studio-2022-<VERSION_BEFORE_17.14.0> sudo dnf versionlock add visual-studio-2022

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

microsoft visual studio 2026 UPGRADE

Affected: >= 18.9.0 and < 18.9.3

Fixed in: 18.9.3

Safe to downgrade to: a release before 18.9.0

1. Check installed version

apt-cache policy visual-studio-2026 || rpm -q visual-studio-2026 || visual-studio-2026 --version

2. UPGRADE to 18.9.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade visual-studio-2026

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade visual-studio-2026

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 18.9.0 (Debian / Ubuntu)

apt-cache madison visual-studio-2026 sudo apt install visual-studio-2026=<VERSION_BEFORE_18.9.0> sudo apt-mark hold visual-studio-2026

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list visual-studio-2026 sudo dnf downgrade visual-studio-2026-<VERSION_BEFORE_18.9.0> sudo dnf versionlock add visual-studio-2026

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-69805?

microsoft.diagnostics.runtime: upgrade to 4.1.740301; visual studio 2022: upgrade to 17.14.40; visual studio 2026: upgrade to 18.9.3. Exact commands for each OS are on this page.

Is CVE-2026-69805 being exploited?

CVE-2026-69805 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-69805 affect?

CVE-2026-69805 affects microsoft.diagnostics.runtime, visual studio 2022, visual studio 2026. Severity is high (CVSS 7.5). External control of file name or path in .NET allows an unauthorized attacker to elevate privileges over a network.

How urgent is CVE-2026-69805?

Priority 42/100. High severity; On your watchlist

Software pages

Visual Studio vulnerabilities

References

← Back to latest CVEs