Skip to main content
Mallory
MediumVulnerability

CVE-2010-0166: Memory Corruption in gfxTextRun::SanitizeGlyphRuns (Firefox Mac OS X)

Published Mar 25, 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.
CVSS5.1Medium · v2
EPSS6.9%94th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Mozilla
IdentifiersCVE-2010-0166CWE-119 · Improper Restriction of Operations…

A vulnerability exists in Mozilla Firefox 3.6 before 3.6.2 on Mac OS X within the gfxTextRun::SanitizeGlyphRuns function in gfx/thebes/src/gfxFont.cpp. When the Core Text API is used, the function does not properly handle certain deletions, leading to memory corruption. This can be triggered by an HTML document containing specific invisible Unicode characters (U+FEFF, U+FFF9, U+FFFA, U+FFFB), potentially allowing remote attackers to crash the application or execute arbitrary code.

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.

Successful exploitation can result in denial of service via application crash or potentially allow remote code execution with the privileges of the user running Firefox. The vulnerability is triggered by specially crafted HTML documents containing certain invisible Unicode characters.

Mitigation

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

As a temporary mitigation, avoid opening untrusted HTML documents or browsing untrusted websites with affected versions of Firefox on Mac OS X. Disabling JavaScript or using security extensions may reduce the attack surface, but upgrading is strongly recommended.

Remediation

Patch, then assume compromise.

Upgrade to Mozilla Firefox version 3.6.2 or later, where the issue in gfxTextRun::SanitizeGlyphRuns has been addressed.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
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
MozillaFirefoxapplication
FAQ

Frequently asked questions

Is CVE-2010-0166 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2010-0166 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2010-0166?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2010-0166. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2010-0166?
Upgrade to Mozilla Firefox version 3.6.2 or later, where the issue in gfxTextRun::SanitizeGlyphRuns has been addressed.
What products are affected by CVE-2010-0166?
Mozilla Firefox.
How severe is CVE-2010-0166?
CVE-2010-0166 has a CVSS v2 score of 5.1 (Medium) and an EPSS score of 6.9% (94th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.