CVE-2009-1537: Legacy DirectShow QuickTime parsing RCE

P0 — ACT NOWCISA KEVRANSOMWARE: UNKNOWNFORENSIC TRIAGE: NO

Quick Answer

CVE-2009-1537 affects the QuickTime Movie Parser Filter in Microsoft's DirectShow component, including the quartz.dll path on legacy Windows systems. Crafted media or streaming content can lead to code execution under the user's rights; the product name does not mean every DirectX installation or Apple's QuickTime application is affected. Check the MS09-028 platform mapping, preserve evidence and retire unsupported systems rather than treating an old patch as restored support.

Fix Or Immediate Action

What to do now: Identify any matching legacy Windows media-processing components and retire or replace the unsupported asset; apply the bulletin's update only where the platform remains supportable.

Open the live Microsoft advisory

Evidence check: Vendor evidence and unresolved source limits are described below. CISA KEV catalog 2026.10.02 was checked on October 2. Preserve the distinction between vendor publication history, catalog dates and evidence from your deployment; no patch or exploit test is claimed.

Context

Scope And Impact In Plain Language

Who should check: Anyone who manages Microsoft DirectX.

When this applies: Only when the exact product, version, and required configuration match the live vendor advisory. Owning the product family alone does not mean the device is vulnerable.

What could happen: A successful attacker may be able to run attacker-chosen commands or software on the affected system, subject to the access and configuration requirements in the advisory.

Not sure? Find the product name and version in the device or application, then compare them with the affected-products section of the linked vendor notice.

Status At A Glance

Product scopeMicrosoft — DirectX
CVECVE-2009-1537
TechGeeks response tierP0 — confirm an exact match and act now
CISA KEV added2026-05-20
Vendor severityCritical for the affected Windows/DirectShow combinations in MS09-028.
CVSSNo numerical CVSS score supplied by the checked historical bulletin.
Ransomware fieldUnknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage fieldNo in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWENot listed in snapshot
Federal remediation date2026-06-03 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

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 media file. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Legacy Windows and DirectX/DirectShow combinations listed in Microsoft bulletin MS09-028, specifically the QuickTime Movie Parser Filter path.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

  1. Confirm. Inventory every DirectX asset and record its exact version, patch level, role, relevant configuration, and exposure.
  2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
  3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
  4. Remediate. Identify any matching legacy Windows media-processing components and retire or replace the unsupported asset; apply the bulletin's update only where the platform remains supportable.
  5. Validate. Confirm the exact legacy OS, DirectX component and historical patch state, then document removal or replacement of the unsupported media-processing path. Test required workflows on the supported replacement; do not open a malicious sample as an operational acceptance test.
  6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Permanent Fix

MS09-028 identifies KB971633 as the historical update for the listed Windows 2000 SP4, Windows XP and Windows Server 2003 DirectX/DirectShow combinations. The package varies with OS, architecture and DirectX version; Vista and Server 2008 are listed as unaffected by this parser issue. Confirm the matching archived package and file-version evidence where needed for recovery, but replace unsupported systems rather than relying on the historical update alone.

Workaround Or Temporary Mitigation

Follow MS09-028 for historical mitigations. Blocking untrusted QuickTime media and isolating legacy systems are temporary risk reductions, not durable remediation.

Important boundary: A workaround, access restriction, or provider-side control may reduce risk while the update is prepared, but it does not necessarily remove vulnerable code or erase an earlier compromise. Install the vendor-approved update when one is available.

Investigation And Recovery

A crafted QuickTime media file can trigger arbitrary code execution. CISA added the CVE to KEV on 2026-05-20; investigate unexpected media-processing activity on any matching host.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: MS09-028 says Microsoft had received exploitation information for CVE-2009-1537 when the bulletin was released. CISA's May 20, 2026 KEV addition is a separate, later catalog event.

CISA statement: CVE-2009-1537 was added to KEV on 2026-05-20. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

References

Wrap-Up

Record whether CVE-2009-1537 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.