Directx vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited19 versions
The short answer

Directx is made by Microsoft. We track 13 published vulnerabilities listed under that exact name, across 19 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 20 May 2026. Microsoft lists newer releases under their own names, such as Directx Files Viewer Control, so check those pages too.

Check your version

The most recent Directx flaw added to the known-exploited list is CVE-2009-1537, on 20 May 2026. We keep watching the known-exploited list.

Other names

Is Directx listed under other names? Yes.

Microsoft also lists Directx under more specific names, such as Directx Files Viewer Control and Directx Media. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Versions

Which versions of Directx do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2009-1537Exploited list, 20 May 2026

    Microsoft DirectX NULL Byte Overwrite Vulnerability

    7.0a7.07.18.1b8.19.0a9.0b9.0
Known exploited

Which Directx vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 8.8
    CVE-2009-1537HighKnown exploited
    Microsoft DirectX NULL Byte Overwrite Vulnerability

    Microsoft DirectX contains a NULL byte overwrite vulnerability in the QuickTime Movie Parser Filter in quartz.dll in DirectShow which could allow remote attackers to execute arbitrary code via a crafted QuickTime...

    Chance of use51%Known exploited since20 May 2026
Exploit likelihood

Which Directx flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 46%

    Stack-based buffer overflow in the DirectShow Synchronized Accessible Media Interchange (SAMI) parser in quartz.dll for Microsoft DirectX 7.0 through 10.0 allows remote attackers to execute arbitrary code via a...

    CVSS8.5Published12 Dec 2007
  2. 39%

    Stack-based buffer overflow in Microsoft DirectX 7.0 and 8.1 on Windows 2000 SP4 allows remote attackers to execute arbitrary code via a Synchronized Accessible Media Interchange (SAMI) file with crafted parameters...

    CVSS9.3Published12 Jun 2008
  3. 36%

    Buffer overflow in Microsoft DirectShow in Microsoft DirectX 7.0 through 10.0 allows remote attackers to execute arbitrary code via a crafted (1) WAV or (2) AVI file.

    CVSS9.3Published12 Dec 2007
  4. 33%

    Multiple integer overflows in a Microsoft Windows DirectX MIDI library (QUARTZ.DLL) allow remote attackers to execute arbitrary code via a MIDI (.mid) file with (1) large length for a Text or Copyright string, or (2)...

    CVSS7.5Published27 Aug 2003
  5. 32%

    Use-after-free vulnerability in DirectShow in Microsoft DirectX 8.1 and 9.0 allows remote attackers to execute arbitrary code via an MJPEG file or video stream with a malformed Huffman table, which triggers an...

    CVSS9.3Published15 Apr 2009
  6. 26%

    IDirectPlay4 Application Programming Interface (API) of Microsoft DirectPlay 7.0a thru 9.0b, as used in Windows Server 2003 and earlier allows remote attackers to cause a denial of service (application crash) via a...

    CVSS5.0Published6 Aug 2004
Precursor Intelligence

Running Directx? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 13 published vulnerabilities listed under the name Directx, across 19 versions. The most recent Directx flaw added to the known-exploited list is CVE-2009-1537, on 20 May 2026.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2009-1537.

Microsoft also lists Directx under more specific names, such as Directx Files Viewer Control and Directx Media. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Each flaw names its own versions, usually as ranges. The newest, CVE-2009-1537, affects 7.0a, 7.0, 7.1, 8.1b and more. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Directx. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.