Microsoft has released security updates to address CVE-2026-4463, a critical remote code execution vulnerability affecting multiple Windows products that could allow attackers to take control of affected systems.
Microsoft has released emergency security updates to address CVE-2026-4463, a critical remote code execution vulnerability affecting multiple Windows products. The vulnerability could allow an attacker to execute arbitrary code with system privileges on vulnerable systems.
The vulnerability exists in the way the Windows Graphics Component handles objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the local system. This could allow the attacker to install programs, view, change, or delete data, or create new accounts with full user rights.
Affected Products:
- Windows 10 Version 21H2 (all editions)
- Windows 10 Version 22H2 (all editions)
- Windows 11 Version 22H2 (all editions)
- Windows 11 Version 23H2 (all editions)
- Windows Server 2022 (all editions)
- Windows Server 2019 (all editions)
CVSS Score: 8.8 (High)
The vulnerability was discovered by Microsoft's internal security team. There is no evidence that this vulnerability has been publicly disclosed or exploited in the wild.
Mitigation Steps:
- Install the security updates immediately from the Microsoft Security Response Center
- For systems that cannot be patched immediately, implement the following workarounds:
- Disable the Windows Graphics Component via Group Policy
- Restrict access to affected graphics libraries
- Enable Windows Defender Antivirus with real-time protection
- Configure Windows Defender Exploit Guard to help protect against exploitation
Timeline:
- Vulnerability discovered: January 2026
- Security updates released: February 2026
- Next security bulletin: March 2026
Microsoft urges all customers to apply these updates as soon as possible. Organizations should prioritize deploying updates to servers and domain controllers before workstations.
For detailed information about the vulnerability and affected files, refer to the Microsoft Security Update Guide.
Comments
Please log in or register to join the discussion