CVE-2011-0073

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 70%
CISA-KEV: Not listedEPSS: 70%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

Mozilla Firefox before 3.5.19 and 3.6.x before 3.6.17, and SeaMonkey before 2.0.14, does not properly use nsTreeRange data structures, which allows remote attackers to execute arbitrary code via unspecified vectors that lead to a "dangling pointer."

CVSS v3
—
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses intrinsic severity with real-world exploitation and automatability, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
99.3%
KEV
Not listed

Published

May 7, 2011

Last Modified

April 29, 2026

References (20)

Vendor Advisories for CVE-2011-0073(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuthunderbird (3.1.10+build1+nobinonly-0ubuntu0.11.04.1) @ natty2026-05-29ubuntu
ubuntuxulrunner-1.9.2 (1.9.2.17+build3+nobinonly-0ubuntu0.10.04.1) @ lucid2026-05-29ubuntu
ubuntuxulrunner-1.9.1 (1.9.1.19+build2+nobinonly-0ubuntu0.9.10.1) @ karmic2026-05-29ubuntu
ubuntuthunderbird (3.1.10+build1+nobinonly-0ubuntu0.10.10.1) @ maverick2026-05-29ubuntu
redhatxulrunner-0:1.9.2.17-4.el6_02011-04-29redhat
redhatseamonkey-0:1.0.9-70.el4_82011-04-29redhat
redhatthunderbird-0:2.0.0.24-17.el5_62011-04-29redhat
redhatthunderbird-0:3.1.10-1.el6_02011-04-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:04 UTCEG score recompute
  2. 2026-07-23 00:39 UTCEG score recompute▼ 6.50
  3. 2026-07-23 00:07 UTCEG score recompute▲ 6.50
  4. 2026-07-22 21:46 UTCEG score recompute
  5. 2026-07-22 14:03 UTCEPSS rescore
  6. 2026-07-20 17:03 UTCEPSS rescore
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-16 16:58 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-11 08:22 UTCEPSS rescore
  12. 2026-07-11 08:22 UTCEPSS rescore
  13. 2026-07-08 15:10 UTCEPSS rescore
  14. 2026-07-08 15:10 UTCEPSS rescore
  15. 2026-07-06 16:23 UTCEPSS rescore
  16. 2026-07-06 02:19 UTCEPSS rescore
  17. 2026-07-06 02:19 UTCEPSS rescore
  18. 2026-07-04 06:27 UTCEPSS rescore
  19. 2026-07-01 15:02 UTCEPSS rescore
  20. 2026-07-01 15:02 UTCEPSS rescore
  21. 2026-06-29 14:02 UTCEPSS rescore
  22. 2026-06-27 03:05 UTCEPSS rescore
  23. 2026-06-27 03:05 UTCEPSS rescore
  24. 2026-06-25 13:46 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 40 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-23 21:30 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-17 17:49 UTCEPSS rescore
  6. 2026-06-17 17:49 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-15 17:44 UTCEPSS rescore
  9. 2026-06-12 23:08 UTCEPSS rescore
  10. 2026-06-11 13:56 UTCEPSS rescore
  11. 2026-06-10 22:14 UTCEPSS rescore
  12. 2026-06-08 14:14 UTCEPSS rescore
  13. 2026-06-08 14:14 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-07 15:22 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 13:44 UTCEPSS rescore
  18. 2026-06-05 22:44 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-05 06:07 UTCEPSS rescore
  21. 2026-06-04 13:09 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-05-31 00:14 UTCEPSS rescore
  24. 2026-05-31 00:14 UTCEPSS rescore
  25. 2026-05-29 13:41 UTCEPSS rescore
  26. 2026-05-29 13:40 UTCEPSS rescore
  27. 2026-05-29 08:03 UTCEG score recompute
  28. 2026-05-29 08:03 UTCVendor advisory
  29. 2026-05-29 08:03 UTCGHSA enrichment
  30. 2026-05-26 07:16 UTCEPSS rescore
  31. 2026-05-26 07:16 UTCEPSS rescore
  32. 2026-05-24 16:43 UTCEPSS rescore
  33. 2026-05-22 21:15 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-18 21:29 UTCEPSS rescore
  40. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-17520✓ verified
    First seen Jul 10, 2011

    Mozilla Firefox - 'nsTreeRange' Dangling Pointer (Metasploit) (1)

    Open source ↗
  • Exploit-DBEDB-17419✓ verified
    First seen Jun 20, 2011

    Mozilla Firefox - 'nsTreeRange' Dangling Pointer (2)

    Open source ↗
  • Metasploitexploit/windows/browser/mozilla_nstreerange✓ verified
    First seen Feb 2, 2011

    Mozilla Firefox "nsTreeRange" Dangling Pointer Vulnerability

    Open source ↗

Frequently asked(4)

What is CVE-2011-0073?
CVE-2011-0073 is a none vulnerability published on May 7, 2011. Mozilla Firefox before 3.5.19 and 3.6.x before 3.6.17, and SeaMonkey before 2.0.14, does not properly use nsTreeRange data structures, which allows remote attackers to execute arbitrary code via unspecified vectors that lead to a "dangling pointer."
When was CVE-2011-0073 disclosed?
CVE-2011-0073 was first published in the National Vulnerability Database on May 7, 2011, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-0073 actively exploited?
CVE-2011-0073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2011-0073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-0073, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-0073

Explore →

Is Your Infrastructure Affected by CVE-2011-0073?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs