Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-62902: Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized attacker to disclose i

42
This month
MEDIUM 6.5WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-62902 is a medium-severity flaw (CVSS 6.5) affecting visual studio 2022, visual studio 2026, .net. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized attacker to disclose information over a network.

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.9% (top 41%)
CISA exploited listNo
WeaknessCWE-693, CWE-829, CWE-918
Published2026-08-11
Last modified2026-08-14
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

microsoft visual studio 2022 UPGRADE
Affected: >= 17.14.0 and < 17.14.38
Fixed in: 17.14.38
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.38 (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.8.0 and < 18.8.3
Fixed in: 18.8.3
Safe to downgrade to: a release before 18.8.0
1. Check installed version
apt-cache policy visual-studio-2026 || rpm -q visual-studio-2026 || visual-studio-2026 --version
2. UPGRADE to 18.8.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.8.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2026 sudo apt install visual-studio-2026=<VERSION_BEFORE_18.8.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.8.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.
microsoft .net UPGRADE
Affected: >= 8.0.0 and < 8.0.30 · >= 9.0.0 and < 9.0.19
Fixed in: 8.0.30, 9.0.19
Safe to downgrade to: a release before 8.0.0
1. Check installed version
apt-cache policy .net || rpm -q .net || .net --version
2. UPGRADE to 8.0.30 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade .net
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade .net
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 8.0.0 (Debian / Ubuntu)
apt-cache madison .net sudo apt install .net=<VERSION_BEFORE_8.0.0> sudo apt-mark hold .net
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list .net sudo dnf downgrade .net-<VERSION_BEFORE_8.0.0> sudo dnf versionlock add .net
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-62902?

visual studio 2022: upgrade to 17.14.38; visual studio 2026: upgrade to 18.8.3; .net: upgrade to 8.0.30, 9.0.19. Exact commands for each OS are on this page.

Is CVE-2026-62902 being exploited?

CVE-2026-62902 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-62902 affect?

CVE-2026-62902 affects visual studio 2022, visual studio 2026, .net. Severity is medium (CVSS 6.5). Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized attacker to disclose information over a network.

How urgent is CVE-2026-62902?

Priority 42/100. On your watchlist

Software pages

Visual Studio vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.