CVE Intelligence
CISA KEV High

CVE-2009-1537 — Microsoft DirectX NULL Byte Overwrite Vulnerability

Unspecified vulnerability in the QuickTime Movie Parser Filter in quartz.dll in DirectShow in Microsoft DirectX 7.0 through 9.0c on Windows 2000 SP4, Windows XP SP2 and SP3, and Windows Server 2003 SP2 allows remote attackers to execute arbitrary code via a crafted QuickTime media file, as exploited in the wild in May 2009, aka "DirectX NULL Byte Overwrite Vulnerability."

Published May 29, 2009 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 51.2% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed May 20, 2026
EPSS FIRST
51.21%
ahead of 99% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Directx and 4 more
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

US federal deadline: Jun 3, 2026 — passed 134 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Directx, Microsoft Windows 2000, Microsoft Windows 2003 Server…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  6. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  7. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Directx version 9.0cversion 7.0version 7.0aversion 7.1version 8.1version 8.1bversion 9.0version 9.0a
and 1 more version 9.0b
Vulnerable NIST National Vulnerability Database
Microsoft Windows 2000 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 2003 Server versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2003 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Xp versions not specified by the source Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
9.3 CVSS 2.0 High 8.6 10.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-158

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
May 20, 2026
Federal deadline
Jun 3, 2026
passed 134 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 51.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before May 20, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/directx, microsoft/windows 2000, microsoft/windows 2003 server, microsoft/windows server 2003, microsoft/windo
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    May 19, 2026 · CISA
  • 2009
  • CVE published
    May 29, 2009 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

16 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2026-05
what else CISA listed that month
CWE-158
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2015-2387 Microsoft ATM Font Driver Privilege Escalation Vulnerability KEV Jul 14, 2015
  • High CVE-2015-2360 Microsoft Win32k Privilege Escalation Vulnerability KEV Jun 9, 2015
  • High CVE-2015-1701 Microsoft Win32k Privilege Escalation Vulnerability KEV Apr 21, 2015
  • High CVE-2014-6324 Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation Vulnerability KEV Nov 18, 2014
  • High CVE-2014-6332 Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution Vulnerability KEV Nov 11, 2014
  • High CVE-2014-4077 Microsoft IME Japanese Privilege Escalation Vulnerability KEV Nov 11, 2014

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2009-1537 is "Microsoft DirectX NULL Byte Overwrite Vulnerability", rated High. It affects Directx (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 51.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.