Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2010-3962: Microsoft Internet Explorer CSS Memory Corruption RCE

Published Nov 5, 2010 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3.1
EPSS96.8%100th percentile
CISA KEVYesAdded Oct 6, 2025
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2010-3962CWE-416 · Use After Free

CVE-2010-3962 is a memory corruption vulnerability affecting Microsoft Internet Explorer 6, 7, and 8. Crafted web content involving Cascading Style Sheets (CSS) token sequences and the clip attribute can trigger arbitrary code execution. The flaw is classified as use-after-free and is also known as an invalid flag reference issue or Uninitialized Memory Corruption Vulnerability. Technical descriptions additionally identify insufficient memory allocation while parsing particular CSS tag combinations, resulting in an overwrite of the least significant byte of a vtable pointer. The vulnerability was exploited in the wild in November 2010 and added to CISA’s Known Exploited Vulnerabilities Catalog in October 2025.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote attackers can execute arbitrary code through the affected browser. Historical exploitation delivered the Pirpi backdoor. Public exploit code is available, and exploitation in real-world attacks is documented. The precise execution privileges and additional confidentiality or availability impacts are not specified.

Mitigation

If you can’t patch tonight, do this now.

Isolate affected legacy systems and restrict their exposure to untrusted web content when immediate patching or retirement is not feasible. Network segmentation, access restrictions, and monitoring for suspicious activity provide compensating controls but do not correct the memory corruption flaw.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates addressing CVE-2010-3962, associated with security bulletin MS10-090. Retire or replace legacy Internet Explorer installations where maintaining a patched deployment is not feasible. Organizations subject to BOD 22-01 must remediate the KEV-listed vulnerability by the applicable catalog deadline.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationInternet Explorerapplication
FAQ

Frequently asked questions

Is CVE-2010-3962 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 6, 2025.
Is there a public exploit for CVE-2010-3962?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2010-3962, the earliest disclosed Nov 3, 2010.
Is there a patch for CVE-2010-3962?
Apply the Microsoft security updates addressing CVE-2010-3962, associated with security bulletin MS10-090. Retire or replace legacy Internet Explorer installations where maintaining a patched deployment is not feasible.
What products are affected by CVE-2010-3962?
Microsoft Corporation Internet Explorer.
How severe is CVE-2010-3962?
CVE-2010-3962 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 96.8% (100th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.