Threats / Microsoft / CVE-2013-3906
CVE-2013-3906
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft Graphics Component vulnerability
Microsoft Graphics Component memory corruption vulnerability enabling remote code execution. Actively exploited in the wild with high EPSS score.
Verdict
Today item — known-exploited.
A memory corruption flaw in Microsoft's Graphics Component allows unauthenticated attackers to execute arbitrary code remotely. The vulnerability has been observed in active exploitation campaigns and poses significant risk to unpatched systems.
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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-02-15).
Probability (EPSS)
EPSS 0.84971 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Graphics Component. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.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 document or media file that triggers unsafe memory operations in the Graphics Component when processed.
Business
Users opening untrusted files face immediate code execution risk, compromising endpoint security and enabling lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the weaponized file via email, web download, or file-sharing to reach target systems at scale.
Business
Attack surface spans all users consuming external content, multiplying incident response burden and breach probability.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access or deploy secondary payloads once code execution is achieved on the victim machine.
Business
Compromised endpoints become staging points for data exfiltration, lateral spread, and long-term adversary presence.
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