On this page (6 sections)

CVE-2026-96067 is a newly published vulnerability in Microsoft Color Management. The NVD record describes it as an integer overflow or wraparound that lets an unauthorized attacker execute code over a network, and it carries a critical CVSS score of 9.8.

If you run Windows servers or workstations, or you manage hosting and web infrastructure on Windows, this is one to track today. Public detail is very limited at the time of writing, so this article separates what is confirmed from what is not, and explains how to get ready to patch.

What is confirmed so far

The NVD entry was published on 2026-11-10. It gives a one-sentence description, a CVSS score of 9.8, a critical severity rating and the weakness type CWE-190. Its only reference is Microsoft's own update guide page for CVE-2026-96067.

Only one independent publisher covers this story so far, and the sources available do not include the vendor advisory text. That means the following are unknown to us: which Windows versions are affected, which update fixes the flaw, what the attacker needs to do to trigger it, and whether anyone is exploiting it. We will not guess at any of these.

The record is not listed in CISA's Known Exploited Vulnerabilities catalog as of the research. That is not proof that no one is exploiting it, only that no such listing exists yet.

What the weakness class means

An integer overflow or wraparound (CWE-190) happens when a program does arithmetic on a number and the result is too big for the space reserved for it. The value wraps around to something small or negative. If the program then uses that value to decide how much memory to allocate or copy, it can allocate too little space and write past the end of it. That kind of memory corruption is a common route to code execution.

Color Management components process data such as color profiles, which are structured files with many size and offset fields. Parsers of structured formats are a common place for this kind of bug. The research does not say how this particular flaw is reached, so treat this as general background rather than a description of the exploit path.

The NVD description says "over a network" and "unauthorized attacker", which suggests the attacker does not need to be an authorized user of the system. Whether user interaction is required is not stated in the research.

Who is realistically exposed

Because the affected versions are not yet confirmed, assume any supported Windows system could be in scope until Microsoft's advisory says otherwise. The highest priority groups are:

  • Internet-facing Windows servers, including those running IIS or other web workloads.
  • Servers that process files or images uploaded by outside users.
  • Shared hosting and remote desktop hosts where many users open untrusted content.
  • Administrator workstations, which hold credentials to many other systems.

Linux-only hosting stacks are not implicated by anything in the research, since the component is Microsoft's.

What to do now

  1. Open Microsoft's update guide entry for CVE-2026-96067 and read the affected products and the fixed build or update number.
  2. Build an inventory of Windows systems, starting with internet-facing servers and anything that handles untrusted files.
  3. Compare each system's installed updates with the fix named by Microsoft.
  4. Test the update on a staging system, then deploy to the most exposed systems first.
  5. Restrict network access to Windows services that do not need to be public, as a stopgap until patched.
  6. Re-check the Microsoft page and CISA KEV daily for changes in exploitation status.

To see which updates are installed on a Windows machine, you can list them with PowerShell. This is a read-only query; run it in an elevated PowerShell window and compare the output with the update identifier in Microsoft's advisory.

List installed Windows updates, newest first (read-only, run in PowerShell)PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20 HotFixID, Description, InstalledOn
Caution. Installing Windows updates often requires a reboot. Schedule the restart for servers in a maintenance window and confirm that failover or backups are in place first.
Tip. Do not rely on third-party blog summaries, including this one, for the fixed version. Take the update number only from Microsoft's advisory.

Detection and monitoring afterwards

Until details are published, there are no confirmed indicators of compromise to hunt for, and we will not invent any. Practical steps that still help:

  • Watch Windows event logs and endpoint protection alerts for unexpected crashes of services that parse images or color profiles, since memory corruption bugs often cause crashes before a working exploit exists.
  • Alert on new processes spawned by web server or file-handling services.
  • Monitor your public Windows-hosted sites for unexpected changes to certificates, DNS records and response headers. Webforta Monitor covers certificate, DNS and header-change monitoring, which can surface tampering after a server compromise, though it does not detect this specific flaw.

If you suspect a server was compromised, follow the steps in Website hacked: what to do and Check if a website is hacked.

Timeline

Known dates for CVE-2026-96067
DateEvent
2026-11-10CVE published in NVD with CVSS 9.8 and CWE-190; the record references Microsoft's update guide page
Not statedPatch release date, exploitation reports and affected versions are not given in the research

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-96067: Integer overflow or wraparound in Microsoft Color Management allows an unauthorized attacker to execute code over a network.nvd.nist.gov ·
  • Microsoft
  • Windows
  • CVE-2026-96067
  • Remote code execution
  • Integer overflow