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

> Remote attackers can execute arbitrary code via a use-after-free vulnerability in Internet Explorer, as exploited during Operation Aurora.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 20 May 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2010
- **Updated:** 21 May 2026
- **Also known as:** GHSA-x2mp-6fmq-52qw

## What is CVE-2010-0249?

CVE-2010-0249 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 15 Jan 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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."

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2010-0249?

It affects 1 product.


Products: Microsoft Internet Explorer.

## How do I fix CVE-2010-0249?

No fix has been published for CVE-2010-0249 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Jun 2026.

## Is CVE-2010-0249 being exploited?

Yes. Attackers have exploited CVE-2010-0249 in the wild since at least 20 May 2026.

Public exploit code:

- MS10-002 Microsoft Internet Explorer "Aurora" Memory Corruption (metasploit)
- Microsoft Internet Explorer 6 - 'Aurora' Memory Corruption (MS10-002) (exploitdb)
- Microsoft Internet Explorer - 'Aurora' Memory Corruption (MS10-002) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Internet Explorer

- [CVE-2014-1776](https://insights.sbomify.com/CVE-2014-1776/): Microsoft Internet Explorer Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2021-27085](https://insights.sbomify.com/CVE-2021-27085/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0222](https://insights.sbomify.com/CVE-2017-0222/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0210](https://insights.sbomify.com/CVE-2017-0210/): Microsoft Internet Explorer Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2017-0149](https://insights.sbomify.com/CVE-2017-0149/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0249 and fix it if it is affected.

What it is: CVE-2010-0249 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 15 Jan 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2010-0249 in the wild since at least 20 May 2026.

Affected product: Microsoft Internet Explorer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-0249/ (Markdown: https://insights.sbomify.com/CVE-2010-0249/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0249
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0249
- OSV: https://osv.dev/vulnerability/CVE-2010-0249

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-0249/
Summaries are generated and may contain mistakes; the official description above is the record.