CVE-2009-2668

CVE-2009-2668 is a high-severity vulnerability in Microsoft Internet Explorer with a CVSS 2.0 base score of 7.8. Its EPSS exploit-prediction score of 14% places it in the 96th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-399.

Key facts

Description

Microsoft Internet Explorer 6 through 6.0.2900.2180 and 7 through 7.0.6000.16473 allows remote attackers to cause a denial of service (CPU consumption) via an XML document composed of a long series of start-tags with no corresponding end-tags, a related issue to CVE-2009-1232.

Frequently asked questions

What is CVE-2009-2668?
Microsoft Internet Explorer 6 through 6.0.2900.2180 and 7 through 7.0.6000.16473 allows remote attackers to cause a denial of service (CPU consumption) via an XML document composed of a long series of start-tags with no corresponding end-tags, a related issue to CVE-2009-1232.
How severe is CVE-2009-2668?
CVE-2009-2668 has a CVSS 2.0 base score of 7.8, rated high severity.
Is CVE-2009-2668 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 14% (96th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-2668?
CVE-2009-2668 primarily affects Microsoft Internet Explorer. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-2668?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2009-2668 published?
CVE-2009-2668 was published on 2009-08-05 and last updated on 2026-06-16.

References

Affected products (2)

More vulnerabilities in Microsoft Internet Explorer

All CVEs affecting Microsoft Internet Explorer →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →