Quick answers
- Is CVE-2026-32225 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32225 being exploited in the wild.
- How severe is CVE-2026-32225?
- High severity, with a CVSS score of 8.8, published 14 April 2026.
- Which products and versions are affected?
- Microsoft Windows 11 22H3, 23H2, 24H2, 25H2, 26H1; Microsoft Windows 10 1607, 1809, 21H2, 22H2; Microsoft Windows Server 2012 R2 and Base.
- Is there a fix for CVE-2026-32225?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-32225 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-32225?
- Check whether you run Microsoft Windows 11, Microsoft Windows 10 or Microsoft Windows Server 2012 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A protection mechanism failure (CWE-693) exists in the Windows Shell component across multiple versions of Windows and Windows Server. The vulnerability is reachable over the network and is triggered when a user interacts with a malicious resource (UI:R). According to the CVSS vector, the exploit can lead to a total loss of confidentiality, integrity, and availability (C:H/I:H/A:H). Microsoft has released security updates to address this issue; administrators should apply the latest cumulative updates for their respective Windows versions.
Affected products
- Microsoft Windows 10 1607, 1809, 21H2, 22H2
- Microsoft Windows 11 22H3, 23H2, 24H2, 25H2, 26H1
- Microsoft Windows Server 2012 R2 and Base
Timeline
- 2026-04-14: disclosed
- 2026-04-14: advisory: Microsoft released the security update guide for this vulnerability.