Exploited CVEs / Microsoft / CVE-2017-0262
CVE-2017-0262
Microsoft Office Remote Code Execution Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-08-10 (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.
Risk summary
Actively exploited Microsoft Office vulnerability. Added to the CISA KEV catalog 2022-02-10.
Senserva AI Opinion for CVE-2017-0262
Microsoft Office grants remote code execution through this flaw when a victim opens attacker-supplied content, and it was exploited in the wild before many organizations had patched. Severity is High with KEV confirmation on 2022-02-10. Office exploits of this vintage persist in commodity phishing kits because they cost attackers nothing and still hit unmanaged machines.
Do this: Check unmanaged and BYOD Windows machines for outdated Office versions and bring them under patch management.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2017-0262
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2017-0262
- Published
- 2022-02-10
- Last revised
- 2022-02-10
- Changes tracked
- 1
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 remediation due date: 2022-08-10 (past due).
Official fix for CVE-2017-0262
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-2017-0262
Is CVE-2017-0262 actively exploited?
Yes. CVE-2017-0262 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-02-10, which means exploitation in the wild has been confirmed, not predicted.
What is the CISA deadline and required action for CVE-2017-0262?
CISA set the federal remediation due date at 2022-08-10, which has passed; treat any unremediated system as overdue.
What fixes CVE-2017-0262?
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-2017-0262?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2017-0262'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 (morning and afternoon US Central).
Scope and sources
- More exploited Microsoft CVEs
- CVE-2019-1068CVE-2008-4250CVE-2009-1537CVE-2010-0249CVE-2010-0806CVE-2026-41091CVE-2026-45498CVE-2026-33825
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.