Exploited CVEs / Microsoft / CVE-2009-0238
CVE-2009-0238
Microsoft Office Remote Code Execution. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-04-28 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Microsoft Security Update Guide (MSRC), linked below.
Actively exploited Microsoft Office vulnerability. Added to the CISA KEV catalog 2026-04-14.
Risk summary
Updated July 25, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2009-0238
CISA put this 2009 Excel remote code execution bug on the KEV list on 2026-04-14, so someone is exploiting it right now against systems that should have been retired long ago. Opening a crafted Excel file with a malformed object hands the attacker complete control of the machine.
Do this: Search for unsupported Office installs still in use, and block legacy binary Excel formats at the email gateway meanwhile.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2009-0238
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2009-0238
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2026-04-28 (past due).
Official fix for CVE-2009-0238
The authoritative fix and affected-version list are published by the vendor. Find the Office advisory on Microsoft Security Update Guide (MSRC).
Common questions about CVE-2009-0238
Is CVE-2009-0238 actively exploited?
Yes. CVE-2009-0238 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-04-14, which means exploitation in the wild has been confirmed, not predicted.
What is the CISA deadline and required action for CVE-2009-0238?
CISA set the federal (BOD 22-01) remediation due date at 2026-04-28, which has passed; treat any unremediated system as overdue.
What fixes CVE-2009-0238?
The authoritative fix is in the vendor advisory: see Microsoft Security Update Guide (MSRC) for the patched Office versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2009-0238?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2009-0238's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
More exploited Microsoft CVEs
The newest Microsoft entries on the CISA KEV catalog:
All Microsoft exploited CVEs on one page: Microsoft vulnerabilities actively exploited.
Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.
