CVE-2026-62900: Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker t
44
This month
MEDIUM 5.9REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE
CVE-2026-62900 is a medium-severity flaw (CVSS 5.9) 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.
Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.
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 sourceNVD · 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-62900?
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, 10.0.11. Exact commands for each OS are on this page.
Is CVE-2026-62900 being exploited?
CVE-2026-62900 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-62900 affect?
CVE-2026-62900 affects visual studio 2022, visual studio 2026, .net. Severity is medium (CVSS 5.9). Improper removal of sensitive information before storage or transfer in .NET allows an unauthorized attacker to disclose information over a network.
How urgent is CVE-2026-62900?
Priority 44/100. Remotely exploitable, no login, no user action; On your watchlist