DirectX
Auto-added after CISA flagged DirectX as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Known exploited vulnerability
CISA's Known Exploited Vulnerabilities (KEV) catalog flagged DirectX (Microsoft) as exploited in the wild — that's why IsItPatched started tracking it. The vulnerability that triggered it:
CVE-2009-1537 ↗ view on NVD
Per-version vulnerability and lifecycle data for DirectX is still being mapped, so no health score is shown yet. Treat it as urgent: identify the exact version you run and confirm it against Microsoft's advisory, then move to a patched, supported release.
Summary iPlain-English security verdict for DirectX, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
DirectX is on CISA's Known Exploited Vulnerabilities (KEV) catalog — it was confirmed under active attack in the wild, which is why CVE-2009-1537 led IsItPatched to start tracking Microsoft's DirectX. Its per-version vulnerability and lifecycle data is still being mapped, so no health score is shown yet. Treat DirectX as urgent: identify the exact version you run and confirm it against Microsoft's security advisory, then move to a patched, supported release.
Disclosure trend iNew CVEs published for DirectX each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
No urgent unpatched issues identified. ✓
Get alerted about DirectX
Be emailed the moment DirectX gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for DirectX — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is DirectX safe and patched?
DirectX is on CISA's Known Exploited Vulnerabilities (KEV) catalog — it was confirmed under active attack in the wild, which is why CVE-2009-1537 led IsItPatched to start tracking Microsoft's DirectX. Its per-version vulnerability and lifecycle data is still being mapped, so no health score is shown yet. Treat DirectX as urgent: identify the exact version you run and confirm it against Microsoft's security advisory, then move to a patched, supported release.
What should I do about DirectX now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against Microsoft's official advisory.
Why is DirectX listed on IsItPatched?
DirectX was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has DirectX been actively exploited?
Yes. CISA added DirectX to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2009-1537. Make sure you are running a patched, supported version of DirectX and confirm it against Microsoft's security advisory.
Similar software we track
More from Microsoft tracked on IsItPatched.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Microsoft's official advisory before you patch or upgrade.