CVE-2012-1889

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-06-08), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 84%CVSS: 8.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Microsoft XML Core Services 3.0, 4.0, 5.0, and 6.0 accesses uninitialized memory locations, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/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. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
84%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 13, 2012

Last Modified

April 22, 2026

Advisory Details (1)

Auto-updated May 2, 2026
Fix referenced — no release confirmed yet.
generic

Microsoft Security Bulletin MS12-043 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-043

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 45× in last 7d / 201× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 912 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 812 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 15:13 UTCEG score recompute
  2. 2026-10-11 15:13 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-11 13:39 UTCEPSS rescoreEPSS 84% · 99th percentile
  4. 2026-10-11 10:54 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-11 06:34 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-11 02:15 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-10 21:53 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-10 17:34 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-10-10 13:16 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-10 08:57 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-10-10 04:38 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-10 00:19 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-10-09 20:00 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-09 15:41 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-10-09 11:22 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-09 07:04 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-09 02:45 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-08 22:27 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-08 18:09 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-08 13:50 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-10-08 09:29 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-08 05:11 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-08 00:52 UTCEG score recompute
  24. 2026-10-08 00:52 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-07 23:39 UTCEPSS rescoreEPSS 84% · 99th percentile
Show 75 more
  1. 2026-10-07 20:33 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  2. 2026-10-07 16:15 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-07 11:54 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-10-07 07:35 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-07 03:17 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-06 22:58 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-06 18:40 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-06 14:22 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-10-06 10:03 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-06 05:44 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-10-06 01:26 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-05 21:06 UTCEG score recompute
  13. 2026-10-05 21:05 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-05 17:37 UTCEPSS rescoreEPSS 84% · 99th percentile
  15. 2026-10-05 16:45 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-05 12:28 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-05 08:09 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-05 03:50 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-04 23:31 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-04 19:13 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-10-04 14:55 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-04 10:36 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-04 06:14 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-10-04 01:56 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-03 21:38 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-10-03 17:19 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  27. 2026-10-03 13:00 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  28. 2026-10-03 08:39 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  29. 2026-10-03 04:21 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  30. 2026-10-03 00:02 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  31. 2026-10-02 19:44 UTCEG score recompute
  32. 2026-10-02 19:44 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-10-02 15:25 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  34. 2026-10-02 11:04 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-10-02 06:46 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  36. 2026-10-02 02:27 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  37. 2026-10-01 22:09 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  38. 2026-10-01 17:47 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-10-01 13:29 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  40. 2026-10-01 09:11 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  41. 2026-10-01 04:53 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  42. 2026-10-01 00:34 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  43. 2026-09-30 20:15 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  44. 2026-09-30 15:57 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  45. 2026-09-30 11:39 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-09-30 07:21 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  47. 2026-09-30 03:02 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  48. 2026-09-29 22:43 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  49. 2026-09-29 18:22 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  50. 2026-09-29 14:04 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  51. 2026-09-29 09:45 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  52. 2026-09-29 05:26 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  53. 2026-09-29 01:08 UTCEG score recompute
  54. 2026-09-29 01:08 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  55. 2026-09-28 20:48 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-09-28 16:30 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  57. 2026-09-28 12:11 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-09-28 07:53 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  59. 2026-09-28 03:34 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-09-27 23:16 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  61. 2026-09-27 21:51 UTCCISA KEV update
  62. 2026-09-27 18:58 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-09-27 14:40 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  64. 2026-09-27 10:21 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  65. 2026-09-27 06:03 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-09-27 01:44 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  67. 2026-09-26 21:23 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  68. 2026-09-26 17:05 UTCEG score recompute
  69. 2026-09-26 17:05 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  70. 2026-09-26 15:52 UTCEPSS rescoreEPSS 84% · 99th percentile
  71. 2026-09-26 12:46 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-09-26 08:26 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  73. 2026-09-26 04:07 UTCEG score recompute
  74. 2026-09-26 04:07 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8
  75. 2026-09-25 23:48 UTCGHSA enrichmentGHSA-hv88-2gcv-6mjq · GitHub severity HIGH · GitHub CVSS 8.8

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 1 GitHub PoC). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Exploit-DBEDB-19186✓ verified
    Published Jun 16, 2012

    Microsoft XML Core Services - MSXML Uninitialized Memory Corruption (MS12-043) (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/browser/msxml_get_definition_code_exec✓ verified
    Published Jun 16, 2012

    MS12-043 Microsoft XML Core Services MSXML Uninitialized Memory Corruption

    Open source ↗
  • GitHub PoCwhu-enjoy/CVE-2012-1889
    Published Sep 25, 2016

    这里保存着我学习CVE-2012-1889这个漏洞的利用所用到的文件

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2012-1889?
CVE-2012-1889 is a critical-severity vulnerability; its CVE record was published on June 13, 2012. Microsoft XML Core Services 3.0, 4.0, 5.0, and 6.0 accesses uninitialized memory locations, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site.
When was the CVE record for CVE-2012-1889 published?
The CVE record for CVE-2012-1889 was published on June 13, 2012. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 22, 2026; the record at its source may have been updated since.
Is CVE-2012-1889 actively exploited?
Yes. CISA added CVE-2012-1889 to the Known Exploited Vulnerabilities catalog on June 8, 2022, affecting Microsoft XML Core Services. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2012-1889?
CVE-2012-1889 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2012-1889?
CVE-2012-1889 affects Microsoft XML Core Services.
How do I remediate CVE-2012-1889?
A fix for CVE-2012-1889 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2012-1889

Explore →

Is Your Infrastructure Affected by CVE-2012-1889?

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

Book a Demo →Browse All CVEs