CVE-2009-0076 in the critical feed json
Microsoft Internet Explorer 7, when XHTML strict mode is used, allows remote attackers to execute arbitrary code via the zoom style directi…
published 2009-02-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0085
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 33.5%
- EPSS 33.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 4
- Exploit-DB
Summary
Microsoft Internet Explorer 7, when XHTML strict mode is used, allows remote attackers to execute arbitrary code via the zoom style directive in conjunction with unspecified other directives in a malformed Cascading Style Sheets (CSS) stylesheet in a crafted HTML document, aka "CSS Memory Corruption Vulnerability."
Timeline
- Published
- First public exploit (EDB-8082)
Exploit prediction
33.54% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-8152 Microsoft Internet Explorer 7 - Memory Corruption (MS09-002) remote, 2009-03-04
- EDB-8082 Microsoft Internet Explorer 7 (Windows 2003 SP2) - Memory Corruption (MS09-002) remote, 2009-02-20
- EDB-8080 Microsoft Internet Explorer 7 - Memory Corruption (MS09-002) remote, 2009-02-20
- EDB-8079 Microsoft Internet Explorer 7 (Windows XP SP2) - Memory Corruption (MS09-002) remote, 2009-02-20
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-002
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6081
vdb-entry, signature
-
vupen.com
/english/advisories/2009/0389
vdb-entry
- zerodayinitiative.com /advisories/ZDI-09-012/
-
us-cert.gov
/cas/techalerts/TA09-041A.html
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2009-0076
- NVD CVE-2009-0076
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.