Skip to content

Systems

CVE-2026-96067

Integer overflow in Microsoft Color Management allows remote code execution.

Major vulnerability. Remote code execution in a Microsoft Windows component (high CVSS 9.8) impacts widely used OSes; broadly disruptive if exploited.

CVSS
9.8Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.90%chance of exploitation in the next 30 daystop 40% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
10 Nov 2026analysed here 12 Nov 2026

Summary

Impact

Remote attackers can trigger an integer overflow via the Color Management subsystem to achieve remote code execution and potential full system compromise.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Microsoft Windows 10 Version 1607>= 10.0.14393.0 and < 10.0.14393.9688Vendor says fixed in: not stated
Microsoft Windows 10 Version 1809>= 10.0.17763.0 and < 10.0.17763.9487Vendor says fixed in: not stated
Microsoft Windows 10 Version 21H2>= 10.0.19044.0 and < 10.0.19044.7846Vendor says fixed in: not stated
Microsoft Windows 10 Version 22H2>= 10.0.19045.0 and < 10.0.19045.7846Vendor says fixed in: not stated
Microsoft Windows 11 version 23H2>= 10.0.22631.0 and < 10.0.22631.7711Vendor says fixed in: not stated
Microsoft Windows 11 Version 23H2>= 10.0.22631.0 and < 10.0.22631.7711Vendor says fixed in: not stated
Microsoft Windows 11 Version 24H2>= 10.0.26100.0 and < 10.0.26100.9974Vendor says fixed in: not stated
Microsoft Windows 11 Version 25H2>= 10.0.26200.0 and < 10.0.26200.9974Vendor says fixed in: not stated
Microsoft Windows 11 version 26H1>= 10.0.28000.0 and < 10.0.28000.3501Vendor says fixed in: not stated
Microsoft Windows 11 Version 26H2>= 10.0.26300.0 and < 10.0.26300.9974Vendor says fixed in: not stated
Microsoft Windows Server 2016>= 10.0.14393.0 and < 10.0.14393.9688Vendor says fixed in: not stated
Microsoft Windows Server 2016 (Server Core installation)>= 10.0.14393.0 and < 10.0.14393.9688Vendor says fixed in: not stated
Microsoft Windows Server 2019>= 10.0.17763.0 and < 10.0.17763.9487Vendor says fixed in: not stated
Microsoft Windows Server 2019 (Server Core installation)>= 10.0.17763.0 and < 10.0.17763.9487Vendor says fixed in: not stated
Microsoft Windows Server 2022>= 10.0.20348.0 and < 10.0.20348.5870Vendor says fixed in: not stated
Microsoft Windows Server 2025>= 10.0.26100.0 and < 10.0.26100.33822Vendor says fixed in: not stated
Microsoft Windows Server 2025 (Server Core installation)>= 10.0.26100.0 and < 10.0.26100.33822Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Microsoft Color Management (Windows Color Management component)
  • Windows (affected editions per Microsoft advisory)

Fix and mitigation

Action required

Immediate action required

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 9 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 9 Nov 2026CISA SSVC assessment: exploitation none
  2. 10 Nov 2026Published2 days later
  3. 11 Nov 2026CVE record last updated1 day later
  4. 12 Nov 2026Analysed by vulneraibility.com1 day later

Common questions

Is CVE-2026-96067 being exploited?

Not confirmed. CVE-2026-96067 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.90% probability of exploitation in the next 30 days.

How severe is CVE-2026-96067?

CVE-2026-96067 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-96067?

Yes. A fix has been recorded for CVE-2026-96067. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-96067 affect?

CVE-2026-96067 affects Microsoft Color Management (Windows Color Management component), Windows (affected editions per Microsoft advisory). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-96067?

Apply Microsoft security updates immediately; prioritize internet-exposed and enterprise hosts.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Patches (1)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com