CVE-2026-70197 .NET and Visual Studio Remote Code Execution Vulnerability
Updated product information in the Software Update table. This is an informational change only.
Microsoft 5 versions
-
The headline was rewritten. 2 new sentences, beginning: “Updated product information in the Software Update table.”
CVE-2026-70197 .NET and Visual Studio Remote Code Execution Vulnerability
Updated product information in the Software Update table. This is an informational change only.
-
3 new sentences, beginning: “Microsoft is aware that the vulnerability for which this CVE was assigned has not been addressed.”
CVE-2026-70197 .NET Remote Code Execution Vulnerability
Microsoft is aware that the vulnerability for which this CVE was assigned has not been addressed. We are working to prepare and test a complete mitigation. We will update this document when there is more information.
-
2 new sentences, beginning: “Updated an acknowledgement.”
CVE-2026-70197 .NET Remote Code Execution Vulnerability
Updated an acknowledgement. This is an informational change only.
-
2 new sentences, beginning: “Updated the Security Updates table to add KB article links for.NET 11.0 and download and KB article links for Microsoft Visual…”
CVE-2026-70197 .NET Remote Code Execution Vulnerability
Updated the Security Updates table to add KB article links for.NET 11.0 and download and KB article links for Microsoft Visual Studio. This is an informational change only; the fixed builds are unchanged.
-
CVE-2026-70197 .NET Remote Code Execution Vulnerability
Out-of-bounds write in.NET allows an unauthorized attacker to execute code over a network.
Versions are compared on the headline and summary the publisher puts in their feed. An edit to the body of an article that leaves both untouched will not appear here.
Why am I seeing this Ranked on source trust — Microsoft
It ranks mainly on source trust: Microsoft is the most reliable outlet we track on this subject, and is the only one on the story so far.
It clears the bar without leading strongly on any one factor. A middling score is not a claim that the story is important — only that nothing about it is weak.
Link-outLink-out, because it scores 0.42, below the 0.50 bar for a write-up. Link-out means we point at the publisher and say nothing of our own.
| Factor | Weight | Score | Contribution | Where it came from |
|---|---|---|---|---|
| Corroboration | 0.35 | 0.39 | +0.135 32% | 1 independent org on the story. Tier-3 aggregators never corroborate — they can show something is circulating, never that it is true. |
| Source trustleads | 0.25 | 1.00 | +0.250 60% | Microsoft is the highest-trust source on this story and is first-party — the organisation announcing its own news. Trust is taken from the best source, not averaged. |
| Pickup rate | 0.20 | 0.00 | +0.000 0% | One counted organisation, so there is no spread to measure — nothing has picked this up to set a rate. |
| Freshness | 0.20 | 0.17 | +0.034 8% | Halves every 10 hours from the newest item on the story. This is the only factor that rewards a story for nothing more than being recent. |
Corroboration counts distinct organisations, once each, and only from tiers 1 and 2. Freshness halves every 10 hours, so this ranking is a snapshot and will differ at the next build.
CVE-2026-70197 affects .NET and Visual Studio through an out-of-bounds write vulnerability. Remote code execution is possible when an unauthorized attacker exploits this flaw over a network. Microsoft has confirmed awareness of the issue but states the vulnerability remains unaddressed at this time.
Microsoft is actively working to develop and test a complete mitigation for the vulnerability. The company indicated it will provide updates to its advisory documentation as more information becomes available regarding the fix and its deployment timeline.
Security updates have been prepared for .NET 11.0 and Microsoft Visual Studio, with corresponding KB articles and download links now available. However, given that Microsoft has not yet fully addressed the underlying vulnerability, organizations should monitor official Microsoft security channels for further guidance on remediation steps.
What happened
Updated product information in the Software Update table. Microsoft is aware that the vulnerability for which this CVE was assigned has not been addressed. We are working to prepare and test a complete mitigation. We will update this document when there is more information. Updated the Security Updates table to add KB article links for.NET 11.0 and download and KB article links for Microsoft Visual Studio. This is an informational change only; the fixed builds are unchanged. Out-of-bounds write in.NET allows an unauthorized attacker to execute code over a network.
Limited impact or meaningful preconditions.
- Impact
- Remote Code Execution
- Product
- .NET and Visual Studio
How this story arrived
Ordered by when each source was first observed, which is what the velocity figure is computed from. Publishers backdate; observed order does not.
- 01 Microsoftfirst-party first seen CVE-2026-70197 .NET Remote Code Execution Vulnerability
Overclock clusters coverage from independent sources and grades it automatically. The figures above are computed, not editorial. This page summarises and links to reporting by the outlets named — follow the links for the original work.