CVE-2012-1522
Microsoft Internet Explorer 9 does not properly handle objects in memory, which allows remote...
Microsoft Internet Explorer 9 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing a deleted object, aka "Cached Object Remote Code Execution Vulnerability."
Exploit likelihood
What each source reports
NVD Score used
Microsoft Internet Explorer 9 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing a deleted object, aka "Cached Object Remote Code Execution Vulnerability."
- Record
CVE-2012-1522- CVSS 2.0
- 9.3 High
AV:N/AC:M/Au:N/C:C/I:C/A:C - Weakness
- CWE-94
- Updated
- 2026-11-02
CVE List No score
Microsoft Internet Explorer 9 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing a deleted object, aka "Cached Object Remote Code Execution Vulnerability."
- Record
CVE-2012-1522- Updated
- 2026-11-02
EUVDEUVD-2012-1540 No score
Microsoft Internet Explorer 9 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing a deleted object, aka "Cached Object Remote Code Execution Vulnerability."
- Record
EUVD-2012-1540- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-8hvh-6jff-3896 No score
Microsoft Internet Explorer 9 does not properly handle objects in memory, which allows remote...
Microsoft Internet Explorer 9 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing a deleted object, aka "Cached Object Remote Code Execution Vulnerability."
- Record
GHSA-8hvh-6jff-3896- Weakness
- CWE-94
- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2012-1522 is a high vulnerability (CVSS 9.3) in Microsoft Internet Explorer, published July 10, 2012. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 20.9%, the 97th percentile. No source names a fixed version.