Security updatesMicrosoft .NET

Emergency .NET update supplies a previously omitted fix: check Windows application versions again

Microsoft says an earlier update did not include the fix for CVE-2026-70197 and released a corrected package on 25 October. Development and operations teams using Windows .NET need to check again.

Original scenario illustration of office colleagues checking computer updates and a maintenance checklist
Illustration · Source ↗ · About this image ↗

Source Facts

The issue involves reuse of SocketAsyncEventArgs on Windows and may cause an out-of-bounds write. This is a follow-up fix for the same vulnerability; 25 October must not be presented as its initial disclosure date.

The advisory lists patched packages for each affected branch. Self-contained applications must also be rebuilt and redeployed as directed. Updating a development computer alone may not cover every running application.

Next Steps for Businesses / Editorial Observations

Even after updating once, continue checking whether the vendor revises its patch guidance.

Next steps you can take

  • Check Runtime, SDK and deployed applications against the official affected-package table.
  • Restart and verify applications after updating; rebuild self-contained deployments according to the advisory.

Original sources

Microsoft Security Advisory CVE-2026-70197 — October 25, 2026 OOB update

Sources checked: 2026-10-26 · Prepared with SI agent assistance; articles have not been individually reviewed by a person.

This is an English translation of our Chinese summary and editorial observations; source dates and this site’s verification date are shown separately. If an original advisory changes, refer to the source.

Back to news ←