Skip to content
Server Security Center
KEVhigh8.8

CVE-2010-0249: Microsoft Internet Explorer Use-After-Free

Microsoft Internet Explorer · listed in the CISA catalog of actively exploited vulnerabilities since 2026-05-20.

CVSS v3.1 (CISA ADP)
8.8
high
EPSS (exploit probability, 30 days)
92%
higher than 99.8% of all CVEs
Added to CISA KEV
2026-05-20
US federal due date 2026-06-03
Automatable (CISA SSVC)
no
technical impact: total

What is CVE-2010-0249?

Use-after-free vulnerability in Microsoft Internet Explorer 6, 6 SP1, 7, and 8 on Windows 2000 SP4; Windows XP SP2 and SP3; Windows Server 2003 SP2; Windows Vista Gold, SP1, and SP2; Windows Server 2008 Gold, SP2, and R2; and Windows 7 allows remote attackers to execute arbitrary code by accessing a pointer associated with a deleted object, related to incorrectly initialized memory and improper handling of objects in memory, as exploited in the wild in December 2009 and January 2010 during Operation Aurora, aka "HTML Object Memory Corruption Vulnerability."

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: microsoft.com/technet/security/advisory/979352.mspx
  • CISA's deadline for US federal agencies: 2026-06-03 (passed) – a useful benchmark for everyone else, too.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.