Threats / Microsoft / CVE-2012-1889
CVE-2012-1889
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft XML Core Services vulnerability
Microsoft XML Core Services contains a memory corruption vulnerability enabling remote code execution. The flaw has been exploited in the wild.
Verdict
Today item — known-exploited.
A memory corruption defect in XML Core Services allows unauthenticated remote attackers to execute arbitrary code by crafting malicious XML input. Active exploitation in the wild elevates risk despite no ransomware association.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
11 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-06-08).
Probability (EPSS)
EPSS 0.83638 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, XML Core Services. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious XML document that triggers a memory corruption condition in the XML parser.
Business
Attackers gain arbitrary code execution on systems processing untrusted XML, enabling data theft, lateral movement, or system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the malicious XML through email, web content, or file sharing to reach vulnerable systems.
Business
Organizations face widespread infection across endpoints that parse XML without proper input validation or patching.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access or exfiltrate sensitive data once code execution is achieved.
Business
Confidentiality and integrity breaches occur, with potential regulatory and reputational damage from data exposure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05