CVE-2026-21514: Microsoft Word OLE protection bypass
Tech GuruQuick Answer
CISA added CVE-2026-21514 to its Known Exploited Vulnerabilities catalog on 2026-02-10, confirming that exploitation has occurred. If you operate Microsoft Office, 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.
Operator action
Update Microsoft 365 Apps or the applicable supported perpetual Office release and verify the installed version against Microsoft's table.
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 — Office |
|---|---|
| CVE | CVE-2026-21514 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-02-10 |
| Vendor severity | Important |
| CVSS | 7.8 (CVSS v3.1 base) |
| 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-807 |
| Federal remediation date | 2026-03-03 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
Microsoft Office Word Reliance on Untrusted Inputs in a Security Decision Vulnerability. Microsoft Office Word contains a reliance on untrusted inputs in a security decision vulnerability that could allow an authorized attacker to elevate privileges locally. 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
Affected Microsoft 365 Apps and supported Microsoft Office releases for Windows and Mac listed in the MSRC advisory.
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. Update Microsoft 365 Apps or the applicable supported perpetual Office release and verify the installed version against Microsoft's table.
- 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
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: No specific Microsoft workaround is safely captured in the current notes. Retain Protected View, attachment scanning, and other normal document protections, but do not treat them as a replacement for updating.
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 crafted Word document can bypass OLE mitigations. CISA lists the CVE as known exploited; review document-delivery and endpoint telemetry for suspicious Office child processes or follow-on execution.
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: Microsoft marked Exploited: Yes at original publication.
CISA statement: CVE-2026-21514 was added to KEV on 2026-02-10. 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
Wrap-Up
Record whether CVE-2026-21514 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.
