Skip to main content
Mallory
HighVulnerability

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

Published Oct 13, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days42 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, enabling an unauthenticated network attacker to corrupt memory and potentially execute arbitrary code. Exploitation requires high attack complexity and no user interaction. The vulnerability was disclosed on October 13, 2026, but the preceding updates omitted the fix; 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 execute arbitrary code in the affected application's security context, potentially compromising its data and operations with high confidentiality, integrity, and availability impacts. The vulnerability does not independently establish execution with administrative privileges.

Mitigation

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

No vendor-specified interim workaround is available. Prioritize remediation of Windows applications that reuse SocketAsyncEventArgs instances across IPv4 and IPv6 datagram sockets.

Remediation

Patch, then assume compromise.

Install corrected Windows runtimes: .NET 8.0.33, 9.0.22, 10.0.14, or 11.0.0-rc.3.26522.148, or later applicable fixed releases. Corresponding SDK options include 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. Update vulnerable runtime package references, including affected .NET 8 Mono runtime packs. Apply the relevant Visual Studio update for SDKs managed through Visual Studio. Restart applications after updating. Rebuild and redeploy self-contained applications because updating the machine-wide runtime does not replace their bundled runtimes. Apply the corrected update even if the October 13 update was installed. The corrected versions are explicitly identified for win-arm64, win-x64, and win-x86; verify corrected win-arm package versions with Microsoft because the available version listings conflict.

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 17, 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 17, 2026, Mallory has found no public exploit for CVE-2026-70197.
Is there a patch for CVE-2026-70197?
Install corrected Windows runtimes: .NET 8.0.33, 9.0.22, 10.0.14, or 11.0.0-rc.3.26522.148, or later applicable fixed releases. Corresponding SDK options include 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 17, 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.