On this page (7 sections)

CVE-2026-96157 is a heap-based buffer overflow in Microsoft Windows Media Foundation. According to the NVD record, it allows an unauthorized attacker to execute code over a network. The record carries a CVSS score of 9.8 and a critical severity rating, and was published on 2026-11-10.

If you run Windows servers or workstations, whether for hosting, an office, or a developer environment, this is one to track today. The public record is short, so this article separates what is confirmed from what is still unknown, and gives you a patch-readiness plan that does not depend on details nobody has published yet.

What is confirmed so far

The only source with technical content is the NVD entry, which summarizes the issue in a single sentence. From it, we can state the following with confidence:

  • The flaw is a heap-based buffer overflow, classified as CWE-122.
  • The affected component is Windows Media Foundation, Microsoft's framework for audio and video handling.
  • The attacker is described as unauthorized, meaning no prior account or privileges are mentioned.
  • The impact is code execution, and the attack vector is described as over a network.
  • The CVSS base score is 9.8, rated critical.

NVD points to Microsoft's update guide entry for CVE-2026-96157 as the reference. That is where the authoritative list of affected Windows builds and the corresponding security updates should be found.

At the time of writing, only one independent publisher covers this story, and the research contains no vendor advisory text, affected version list, fixed build numbers, or proof of exploitation. Anything beyond the points above would be speculation, so this article does not offer it.

Understanding the weakness in plain terms

A heap-based buffer overflow happens when a program writes more data into a block of memory than the block was sized to hold. The extra data spills into neighboring memory on the heap, the area programs use for dynamically allocated data. If an attacker can control what spills over, they may corrupt program state and, in the worst cases, redirect execution to code of their choosing. That is why this bug class so often ends in remote code execution.

Media frameworks parse complex, structured file and stream formats, and parsers for rich formats are a classic place for length and size mistakes, because they read sizes from untrusted input. The NVD summary does not say which format or function is involved, and we should not guess. What matters operationally is the combination NVD does state: network reachable, no authorization, code execution.

Who is realistically exposed

The research does not list affected Windows versions, so you cannot yet rule any system in or out by version alone. A sensible way to prioritize until Microsoft's guidance is checked:

  • Internet-facing Windows servers, including those handling uploads, previews, thumbnails or transcoding of user-supplied media.
  • Windows systems in shared hosting or build pipelines that open files from outside parties.
  • Domain-joined servers and workstations that an attacker could reach after a first foothold, since a network-reachable flaw also helps lateral movement.
  • Remote desktop and terminal servers where many users share one Windows installation.

Whether the flaw can be reached without any user action, or needs a user to open or stream media, is not stated in the research. Treat the network vector as real until Microsoft's entry says otherwise.

How to check your exposure

Start by reading the Microsoft entry and matching it to your inventory. Then confirm what is installed on each machine. The following read-only command lists recently installed Windows updates, so you can compare against the update Microsoft names for this CVE. Run it in PowerShell on the Windows host and look for the KB number from the Microsoft entry.

List installed Windows updates, newest first (run in PowerShell on the Windows host)PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20 HotFixID, Description, InstalledOn

To record the exact Windows version and build for comparison with the affected builds in Microsoft's entry, this read-only command prints them. Run it in PowerShell; the output shows the product name and build number.

Show Windows product name and build number (run in PowerShell)PowerShell
Get-ComputerInfo -Property WindowsProductName, WindowsVersion, OsBuildNumber
Tip. Build a quick inventory first: hostname, Windows version, build, internet exposure, and whether the host processes untrusted media. That one table makes it easy to decide patch order within minutes of the vendor details being confirmed.

What to do now

  1. Open Microsoft's update guide entry for CVE-2026-96157 and note the affected products, builds and the security update that fixes it.
  2. Inventory your Windows systems and mark which ones are internet-facing or handle untrusted media.
  3. Install the Microsoft security update on exposed systems first, then the rest, following your normal change process.
  4. Reboot where the update requires it, and re-run the update check to confirm the fix is present.
  5. Restrict inbound network access to Windows servers to only the ports and sources they need, so a network-reachable bug has fewer paths in.
  6. Where a server does not need to process media from outside, stop it from doing so until it is patched.
  7. Make sure endpoint protection and logging are active on exposed hosts so unusual crashes or process launches are visible.
  8. Re-check Microsoft's entry over the coming days for updated details, mitigations and any exploitation notice.
Caution. Applying updates and rebooting production servers interrupts services. Test on a representative system where you can, schedule a maintenance window, and keep a rollback plan. Do not delay patching internet-facing systems longer than necessary.

Detection and monitoring after patching

No indicators of compromise, exploit signatures or in-the-wild activity are given in the research, so there is nothing specific to hunt for yet. General signals still help for a memory-corruption bug in a media component:

  • Repeated crashes of media-handling processes or services, visible in the Windows Event Viewer application log.
  • Unexpected child processes started by services that parse media.
  • New outbound connections from servers that normally make none.
  • Unexplained new accounts, scheduled tasks or services shortly after a crash.

Outside-in checks complement host patching. A security scan of your public site can show what your internet-facing services expose, and certificate, DNS and header-change monitoring helps you notice unexpected changes. Neither replaces installing the Microsoft update, and neither is a statement that this specific flaw is detected. For guidance on telling whether a system has already been compromised, see how to check if a website is hacked, and if you find signs of compromise, read website hacked: what to do.

What we do not know yet

  • Which Windows versions and builds are affected.
  • Which update contains the fix, and whether workarounds exist.
  • Whether the flaw requires any user interaction or a specific media format.
  • Whether it is being exploited, or whether public proof-of-concept code exists.
  • Whether Microsoft or other parties will revise the severity or the description.

We will treat these as open questions until Microsoft's entry or other primary sources state otherwise. A CVSS 9.8 rating is a reason to prioritize patching, not proof that attacks are under way.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-96157: Heap-based buffer overflow in Microsoft Windows Media Foundation allows an unauthorized attacker to execute code over a network.nvd.nist.gov ·
  • Windows
  • CVE-2026-96157
  • Remote code execution
  • Patch management
  • Media Foundation