Skip to main content
Mallory
HighVulnerability

CVE-2026-70197: Remote Code Execution in .NET SocketAsyncEventArgs on Windows

Published Oct 13, 2026 · Updated 6 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days36 mentions · peak 7 in a dayToday
CVSS8.1High · v3.1
EPSS0.79%57th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-70197CWE-787 · Out-of-bounds Write

CVE-2026-70197 is an out-of-bounds write vulnerability in the .NET System.Net.Sockets component on Windows. Reusing a SocketAsyncEventArgs instance across IPv4 and IPv6 datagram sockets can leave an undersized cached native address buffer. A subsequent ReceiveFromAsync operation can write beyond that buffer, allowing an unauthenticated network attacker to corrupt memory and potentially execute arbitrary code. Affected Windows runtime package ranges include .NET 8.0.0 through versions before 8.0.33, 9.0.0 through versions before 9.0.22, 10.0.0 through versions before 10.0.14, and 11.0.0-preview.1 through versions before 11.0.0-rc.3.26522.148. Affected .NET 8 packages include both CoreCLR and Mono runtime packs. The vulnerability was disclosed on October 13, 2026, but the fix was missing from the initial updates; corrected packages were issued on October 25, 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can enable unauthenticated remote code execution within the affected .NET application, potentially compromising the confidentiality, integrity, and availability of resources accessible to that process. Memory corruption can also disrupt application availability. The vulnerability has a CVSS v3.1 base score of 8.1, reflecting network exploitation with high attack complexity, no required privileges, and no user interaction.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific interim workaround is documented. Prioritize remediation of network-accessible Windows applications that reuse SocketAsyncEventArgs instances across IPv4 and IPv6 datagram sockets.

Remediation

Patch, then assume compromise.

Install the corrected runtime for the applicable branch: .NET 8.0.33, 9.0.22, 10.0.14, or 11.0.0-rc.3.26522.148, or a later applicable fixed release. Corresponding corrected SDKs are 8.0.133 or 8.0.427; 9.0.123 or 9.0.320; 10.0.114 or 10.0.403; and 11.0.100-rc.3.26522.148. Apply the corrected update even if the October 13 update was installed. Update affected runtime package references and restart applications after updating shared runtimes. Rebuild and redeploy self-contained applications and affected container images, because updating the host runtime does not replace bundled runtimes. Update Visual Studio-managed SDKs through the Visual Studio Installer. For win-arm packages, verify corrected versions with Microsoft because the available package tables contain inconsistent version information.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft Corporation.Net 10.0 Installed On Linuxapplication
Microsoft Corporation.Net 10.0 Installed On Mac Osapplication
Microsoft Corporation.Net 10.0 Installed On Windowsapplication
Microsoft Corporation.Net 11.0 Installed On Linuxapplication
Microsoft Corporation.Net 11.0 Installed On Mac Osapplication
Microsoft Corporation.Net 11.0 Installed On Windowsapplication
Microsoft Corporation.Net 8.0 Installed On Linuxapplication
Microsoft Corporation.Net 8.0 Installed On Mac Osapplication
Microsoft Corporation.Net 8.0 Installed On Windowsapplication
Microsoft Corporation.Net 9.0 Installed On Linuxapplication
Microsoft Corporation.Net 9.0 Installed On Mac Osapplication
Microsoft Corporation.Net 9.0 Installed On Windowsapplication
Microsoft CorporationMicrosoft Visual Studio 2019 Version 16.11application
Microsoft CorporationMicrosoft Visual Studio 2026 Version 18.10application
Microsoft CorporationMicrosoft Visual Studio 2026 Version 18.11application
Microsoft CorporationMicrosoft Visual Studio 2026 Version 18.12application
Microsoft CorporationNetapplication
Microsoft CorporationVisual Studio 2022application
FAQ

Frequently asked questions

Is CVE-2026-70197 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-70197 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-70197?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-70197.
Is there a patch for CVE-2026-70197?
Install the corrected runtime for the applicable branch: .NET 8.0.33, 9.0.22, 10.0.14, or 11.0.0-rc.3.26522.148, or a later applicable fixed release. Corresponding corrected SDKs are 8.0.133 or 8.0.427; 9.0.123 or 9.0.320; 10.0.114 or 10.0.403; and 11.0.100-rc.3.26522.148.
What products are affected by CVE-2026-70197?
Microsoft Corporation Net, Microsoft Corporation Microsoft Visual Studio 2019 Version 16.11, Microsoft Corporation Microsoft Visual Studio 2026 Version 18.10, Microsoft Corporation Microsoft Visual Studio 2026 Version 18.11, Microsoft Corporation Microsoft Visual Studio 2026 Version 18.12, and 13 more.
How severe is CVE-2026-70197?
CVE-2026-70197 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.79% (57th percentile) as of Nov 11, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.