Knox CVE Database
/
CVE-2009-0238
Critical
9.3

CVE-2009-0238: 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.

Added to the CISA KEV catalog:
April 14, 2026

Overview

A memory corruption flaw in Microsoft Excel's file parser allows arbitrary code execution when a user opens a specially crafted spreadsheet containing a malformed object. Affected versions span Excel 2000 through 2007 on Windows, Excel in Office 2004 and 2008 for Mac, Excel Viewer, and the Office Compatibility Pack. Successful exploitation gives an attacker complete control of the target system. This flaw was actively exploited in the wild as early as February 2009, including by the Trojan.Mdropper.AC dropper.

Vulnerability details

Affected vendor
Microsoft
Affected product
Office
Weakness type (CWE)
CWE-94

Excel's file parser fails to safely handle object records within a crafted spreadsheet. When the parser encounters a malformed object, it attempts to access an invalid memory location, producing a memory corruption condition that the attacker can direct toward arbitrary code execution. The weakness falls under improper control of code generation: untrusted file content crosses a trust boundary and is processed in a way that allows attacker-supplied data to influence execution flow. The vendor's fix modifies how Excel opens and processes file objects to prevent the invalid access.


An attacker gets a specially crafted Excel file to a target and waits for the user to open it. No authentication or elevated privilege is required on the attacker's side; the only precondition is that the victim opens the file. Once the malformed object triggers the invalid access, the attacker gains complete control of the affected system, including the ability to install programs, read or modify data, and create new accounts. Privilege level at exploitation matches the logged-in user's rights.

Severity and impact

9.3
Critical
AV:N/AC:M/Au:N/C:C/I:C/A:C
Attack vector
Network
Attack complexity
Medium
Privileges required
User interaction
Scope
Confidentiality impact
Complete
Integrity impact
Complete
Availability impact
Complete

Exploitation status

This vulnerability is confirmed as actively exploited in the wild — it is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

Known ransomware campaign use
Unknown

Detection and monitoring

  • Monitor for Excel processes spawning unexpected child processes such as cmd.exe, powershell.exe, or wscript.exe immediately after a file is opened, which indicates post-exploitation activity rather than normal spreadsheet use.
  • Audit endpoints for files matching Trojan.Mdropper.AC indicators, the specific dropper confirmed to exploit this flaw in the wild in February 2009.

Remediation

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Federal (FCEB) remediation due date
April 28, 2026

Additional hardening

  • Apply the security update delivered in Microsoft Security Bulletin MS09-009 (April 2009) for all affected Excel versions on Windows and Mac, including Excel Viewer and the Office Compatibility Pack.
  • Disable automatic opening of Excel files from email clients and browsers; require users to save attachments before opening, reducing the attack surface for file-based delivery.
  • Apply Microsoft Office File Block policy via Group Policy or registry settings to restrict Excel from opening older binary file formats from untrusted locations, limiting exposure to crafted files.
  • Run Office applications under a least-privilege user account so that successful exploitation does not grant administrative rights to the attacker.

Key dates

Published (NVD)
February 25, 2009
Added to CISA KEV
April 14, 2026
Remediation deadline
April 28, 2026
Last updated
June 16, 2026

References

Frequently asked questions

Does CVE-2009-0238 affect my FedRAMP authorization?

If Microsoft Office runs inside your authorization boundary, yes. CVE-2009-0238 appears in CISA's Known Exploited Vulnerabilities (KEV) catalog, and its remediation deadline of April 28, 2026 has already passed. For a FedRAMP-authorized service, an unpatched KEV in the boundary is a finding. An overdue one is a finding your assessor and sponsoring agency can already see. Your options now are to remediate it or formally document the mitigation and the delay.

How does Knox help me handle CVE-2009-0238?

Knox does not patch your software. Remediating Microsoft Office is your responsibility under the FedRAMP shared-responsibility model. What Knox provides is the pre-authorized, single-tenant boundary to remediate within, along with continuous compliance monitoring and audit-artifact coverage to help you document the fix for your next assessment. The remediation work is yours to carry out; maintaining a defensible compliance posture while you do it is not something you have to manage on your own.

How does Knox's monitoring help with vulnerabilities like this?

Knox's automated continuous monitoring platform watches your environment for newly disclosed vulnerabilities and compliance issues on a continuous basis. For a case like CVE-2009-0238, exposure surfaces during ongoing monitoring rather than waiting until an assessor flags it at a scheduled review. That difference in timing gives you more room to act before a finding becomes a formal conversation with your agency.

How do I get FedRAMP authorized with Knox?

Knox runs a FedRAMP-as-a-Service platform. It gives SaaS vendors a pre-authorized cloud boundary on AWS, Azure, and GCP. Your application inherits 60-80% of the required security controls. You reach FedRAMP authorization in about 90 days for roughly 90% less than the traditional $3.5M path. Book a meeting and Knox will map your path to authorization.

CVE-2009-0238's remediation deadline of April 28, 2026 has passed. What happens now?

If CVE-2009-0238 remains unremediated, it is already a Plan of Action and Milestones (POA&M) item. A growing POA&M list is what turns a routine continuous-monitoring review into a difficult conversation with your sponsoring agency. Closing it out now and documenting why the deadline was missed is what keeps your authorization standing and the agency relationship in good order.

Access continuous compliance

We never compromise on security. Meet with our team to discuss scope, readiness, and map your company’s accelerated path to government certification.