CVE-2008-0015: Legacy Windows Video ActiveX Control RCE

Quick Answer

CISA added CVE-2008-0015 to its Known Exploited Vulnerabilities catalog on 2026-02-17, confirming that exploitation has occurred. If you operate Microsoft Windows, identify the exact version and relevant configuration now, preserve security evidence, and follow the live vendor remediation. A KEV match does not prove your system was compromised, and installing an update does not rule out earlier exploitation.

Last verified: 2026-09-17 UTC. CISA KEV snapshot version 2026.09.16. Recheck the live advisory before changing production.

Context

Status At A Glance

Product scope	Microsoft — Windows
CVE	CVE-2008-0015
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-02-17
Vendor severity	Consult Microsoft bulletin MS09-032; not safely established in the current primary-source notes.
CVSS	Consult Microsoft bulletin MS09-032; not safely established in the current primary-source notes.
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	Not listed in snapshot
Federal remediation date	2026-03-10 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Microsoft Windows Video ActiveX Control Remote Code Execution Vulnerability. Microsoft Windows Video ActiveX Control contains a remote code execution vulnerability. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. 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 Video ActiveX Control and operating-system combinations identified in Microsoft's MS09-032 bulletin.

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 Windows 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. Find and retire affected legacy Windows systems; apply the historical Microsoft update only as an interim step where the asset cannot yet be removed.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
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

Verified fixed release, patch level, or update guidance captured at the last check:

A fixed build or KB was not safely preserved in the research record. Check the live vendor advisory before production changes; do not infer a fixed version from this summary.

Mitigation boundary: Use Microsoft's archived MS09-032 guidance for historical mitigations. Blocking the control or untrusted web content is temporary containment, not durable remediation for an unsupported platform.

A workaround, access restriction, or provider-side control reduces a described path; it does not necessarily remove vulnerable code or erase compromise.

Investigation And Recovery

A specially crafted web page can trigger remote code execution with the logged-on user's rights. CISA added the CVE to KEV on 2026-02-17; review browser and endpoint evidence on any matching legacy 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: Legacy Microsoft bulletin; a modern MSRC exploitation-at-publication field was not safely established in the current notes. CISA KEV status is current and separate.

CISA statement: CVE-2008-0015 was added to KEV on 2026-02-17. 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

• Security Hot Page
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Microsoft advisory or support notice
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2008-0015 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.