CVE-2009-0238: Legacy Microsoft Excel file remote code execution
Tech GuruQuick Answer
CVE-2009-0238 requires a user to open a crafted Excel file containing a malformed object; receiving an email alone is not the exploit. Code runs with the logged-on user's rights, so complete system control is conditional on those rights. Use MS09-009 to identify affected legacy Excel, Viewer and Mac components, preserve file-delivery evidence, and replace unsupported installations. Its historical updates are not a current support guarantee.
Fix Or Immediate Action
What to do now: Find affected legacy Office installations, apply the historical security update where applicable, and migrate unsupported Office versions to a supported release.
Evidence check: The vendor evidence and its limits are described below. CISA KEV catalog 2026.10.02 was checked October 2; catalog chronology is separate from vendor publication history and evidence of compromise in your deployment. No exploit or update test is claimed.
Context
Scope And Impact In Plain Language
Who should check: Anyone who manages Microsoft Office.
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 scope | Microsoft — Office |
|---|---|
| CVE | CVE-2009-0238 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-04-14 |
| Vendor severity | Critical for Excel 2000 SP3; Important for the other listed Excel, Viewer, Compatibility Pack and Mac products in the CVE-specific MS09-009 table. |
| CVSS | No numerical CVSS score supplied by the checked MS09-009 bulletin. |
| 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 | CWE-94 |
| Federal remediation date | 2026-04-28 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
Microsoft Office Remote Code Execution. Microsoft Office Excel contains a remote code execution vulnerability that could allow an attacker to take complete control of an affected system if a user opens a specially crafted Excel file that includes a malformed object. 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 Microsoft Office and Excel releases listed in Microsoft bulletin MS09-009.
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
- Confirm. Inventory every Office asset and record its exact version, patch level, role, relevant configuration, and exposure.
- Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
- Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
- Remediate. Find affected legacy Office installations, apply the historical security update where applicable, and migrate unsupported Office versions to a supported release.
- Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
- 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-009 lists these historical packages. Excel 2007 SP1 requires both its Excel package and the Compatibility Pack update; one alone does not satisfy the bulletin. Match architecture and package prerequisites in the original table, and migrate unsupported software.
| Product | Historical package |
|---|---|
| Excel 2000 SP3 | KB959964 |
| Excel 2002 SP3 (Office XP) | KB959988 |
| Excel 2003 SP3 | KB959995 |
| Excel 2007 SP1 | KB959997 AND Compatibility Pack SP1 KB960003 |
| Office 2004 for Mac | KB968695 |
| Office 2008 for Mac | KB968694 |
| Excel Viewer 2003 SP3 | KB959993 |
| Excel Viewer | KB960000 |
| Compatibility Pack SP1 | KB960003 |
Workaround Or Temporary Mitigation
Use MS09-009 for historical mitigation details. Blocking untrusted Excel files and isolating legacy systems are temporary controls, 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
Opening a specially crafted Excel file containing a malformed object can permit remote code execution. CISA added the CVE to KEV on 2026-04-14; review file-delivery and endpoint evidence on matching legacy hosts.
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: In MS09-009's CVE-2009-0238 FAQ, Microsoft says it had received reports of exploitation when the bulletin was released. Do not transfer the adjacent CVE-2009-0100's no-exploitation statement to this flaw. CISA added this entry on April 14, 2026.
CISA statement: CVE-2009-0238 was added to KEV on 2026-04-14. 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
- TechGeeks Security Notice Center
- 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
Wrap-Up
Record whether CVE-2009-0238 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.
