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

> Remote attackers can execute arbitrary code via a use-after-free vulnerability in Internet Explorer's Peer Objects component.

- **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:** 10 Mar 2010
- **Updated:** 21 May 2026
- **Also known as:** GHSA-f5rx-x946-jm33

## What is CVE-2010-0806?

CVE-2010-0806 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 10 Mar 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 the Peer Objects component (aka iepeers.dll) in Microsoft Internet Explorer 6, 6 SP1, and 7 allows remote attackers to execute arbitrary code via vectors involving access to an invalid pointer after the deletion of an object, as exploited in the wild in March 2010, aka "Uninitialized Memory Corruption Vulnerability."

Weakness: CWE-399, CWE-416 (Use After Free)

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

It affects 1 product.


Products: Microsoft Internet Explorer.

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

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

## Is CVE-2010-0806 being exploited?

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

Public exploit code:

- MS10-018 Microsoft Internet Explorer DHTML Behaviors Use After Free (metasploit)
- Microsoft Internet Explorer - 'iepeers.dll' Use-After-Free (Metasploit) (exploitdb)
- Microsoft Internet Explorer - DHTML Behaviour Use-After-Free (MS10-018) (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-0806 and fix it if it is affected.

What it is: CVE-2010-0806 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 10 Mar 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-0806 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-0806/ (Markdown: https://insights.sbomify.com/CVE-2010-0806/index.md)
```

## Sources

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

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