Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-21509: Microsoft Office COM/OLE Security Feature Bypass

Published Jan 26, 2026 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days10 mentions · peak 3 in a dayToday
CVSS7.8High · v3.1
EPSS70.8%99th percentile
CISA KEVYesAdded Jan 26, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2026-21509CWE-807 · Reliance on Untrusted Inputs in a…

CVE-2026-21509 is a Microsoft Office security feature bypass caused by reliance on untrusted input in a security decision involving COM/OLE object activation. Crafted Office documents can instantiate the Shell.Explorer.1 OLE object, invoking the legacy Internet Explorer engine to access external resources despite intended security restrictions. Observed malicious RTF documents retrieved remote Windows shortcuts over WebDAV, enabling payload execution without additional prompts or macro activation after the document was opened. Affected products include Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, and Microsoft 365 Apps for Enterprise. Microsoft released emergency updates on January 26, 2026, after exploitation in the wild.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation bypasses Office security protections and enables document-based initial-access chains that execute attacker-supplied payloads in the victim's context. Observed campaigns deployed Covenant Grunt implants, PixyNetLoader, and email-surveillance backdoors, supporting remote command execution, persistence, reconnaissance, and data theft. The vulnerability is a security feature bypass; subsequent malware and chained vulnerabilities determine the extent of compromise. It does not independently establish elevated or SYSTEM privileges.

Mitigation

If you can’t patch tonight, do this now.

If immediate updating is not possible, apply Microsoft's registry-based workaround to block activation of the implicated Shell.Explorer.1 OLE class. This may disrupt legitimate documents using that object. On January 28, 2026, 0patch offered third-party micropatches implementing equivalent activation blocking for Office 2010, Office 2013, and click-to-run Office 2016 and 2019; these were a broader countermeasure rather than an independently reproduced vulnerability-specific fix. Restrict unnecessary outbound WebDAV access and detect documents embedding the implicated OLE object as additional compensating controls.

Remediation

Patch, then assume compromise.

Install Microsoft's applicable security updates for the exact Office edition and servicing channel, beginning with the emergency updates released January 26, 2026. Identified minimum fixed versions include 16.0.5539.1001 for Office 2016 and 16.0.10417.20095 for Office 2019. Migrate unsupported installations to a supported, fully updated Office release. Patching does not remove existing implants; systems with suspected exploitation require investigation and incident remediation.

Public exploits

Exploits

5 exploits validated by Mallory's analysis. Hidden: 12 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
cve-2026-21509-office_security_bypass_reproductionRepository contains a small standalone proof-of-concept for CVE-2026-21509 with two files: a README describing the vulnerability and exploit theory, and a single Python script, exploit.py, that acts as the entry point. The script uses argparse to accept an output filename, payload command, CLSID, and a --docx switch. Its core capability is generating malicious Office documents (.doc/.rtf by default, or .docx) containing crafted OLE object data intended to bypass Microsoft Office Protected View / kill-bit style protections. The exploit structure is straightforward: build_ole_object_data() creates a compressed binary blob containing the attacker-chosen CLSID and payload command encoded as UTF-16LE; generate_rtf_doc() embeds that blob into an RTF \object/\objdata structure; generate_docx_with_ole() creates a minimal DOCX ZIP container with standard Office XML parts and an embedded oleObject1.bin referenced from document relationships. The default CLSID is the DHTML Edit Control {0002DF01-0000-0000-C000-000000000046}, and the default payload command is calc.exe. There are no network callbacks, hardcoded IPs, or remote C2 endpoints in the code. The observable artifacts are local file paths inside the generated DOCX package and the embedded CLSID. Overall, this is an operational PoC document generator for a file-based client-side Office exploit, not a scanner or detection script.razureink · Disclosed Jul 23, 2026 · markdown · python · file · localOperationalAshwesker-CVE-2026-21509Repository contains a single Python proof-of-concept script and a README describing CVE-2026-21509 as a Microsoft Office security feature bypass involving OLE/embedded content. Structure & purpose: - `CVE-2026-21509.py`: Generates a DOCX with low-level OpenXML elements (a `w:drawing`/`wp:inline` structure with `a:graphicData` set to the DrawingML picture URI) and creates a separate OLE binary blob (`embedded_ole.bin`). The script’s intent is to help researchers test how Office handles embedded OLE objects/CLSID activation in allegedly vulnerable builds. - `README.md`: Provides background, affected product list, and usage steps. It explicitly frames this as research/testing in an isolated VM and suggests follow-on tooling (oletools, OleViewDotNet, ProcMon) and mitigations (kill bit/patching). Exploit capabilities (as implemented): - User-assisted attack vector: produces a document artifact that must be opened in Office. - Configurable CLSID embedding: `--clsid` controls the COM CLSID written into the OLE stream (little-endian UUID bytes). - No actual code execution/payload: `generate_ole_stream()` builds only a minimal header + CLSID + padding; the script does not embed the OLE binary into the DOCX package relationships/parts in a way that would reliably trigger OLE activation. It prints that manual embedding may be required. Overall assessment: - This is a conceptual/document-generation PoC rather than an operational exploit. It is primarily useful for creating test artifacts and as a starting point for further manual crafting of OLE parts/ActiveX embedding rather than delivering a complete bypass chain.Ashwesker · Disclosed Jan 27, 2026 · python · markdown · local / user-assisted (phishing-style document open)PoCAshwesker-CVE-2026-21509Repository contains a single Python proof-of-concept script and a README describing CVE-2026-21509 as a Microsoft Office security feature bypass involving embedded OLE/COM content. Structure & purpose: - `CVE-2026-21509.py`: Generates a DOCX with low-level OpenXML elements (via `python-docx` + direct XML manipulation) and creates a minimal OLE-like binary stream containing a user-supplied COM CLSID. The script writes the stream to `embedded_ole.bin` and saves the DOCX to a user-chosen path. Comments explicitly state it is conceptual and that real exploitation would require a real vulnerable CLSID and a properly embedded binary part inside the DOCX package. - `README.md`: Provides background, affected Office versions, and testing guidance (run script, open in a vulnerable VM, monitor with ProcMon). It suggests extending the PoC with oletools/VBA/ActiveX, but those capabilities are not implemented in code. Exploit capabilities (as implemented): - Client-side document generation for research/testing. - Embeds a chosen CLSID into a padded binary blob intended to represent an OLE stream. - Does not implement delivery, network callbacks, macro execution, or code execution; it is primarily a scaffold to help researchers craft/test OLE embedding and observe Office behavior. Notable targeting/IOCs: - Writes `embedded_ole.bin` and a DOCX (default `CVE-2026-21509_Test.docx`). - Uses OpenXML namespace URI `http://schemas.openxmlformats.org/drawingml/2006/picture` in document XML (not an external request). - References monitoring `HKCR\CLSID\{...}` for COM activation during testing.kimstars · Disclosed Jan 27, 2026 · python · markdown · client-side document / user-interaction (phishing-style) via opening crafted DOCX with embedded OLE/COM objectPoCCVE-2026-21509-PoCRepository contains a single Python proof-of-concept script plus documentation and pinned dependencies. The PoC claims to relate to CVE-2026-21509 (Microsoft Office security feature bypass) and focuses on generating a DOCX with low-level OpenXML elements intended to represent an embedded object, alongside a separately generated minimal OLE binary stream. Structure & purpose: - CVE-2026-21509.py: Main PoC generator. Uses python-docx to create a Word document, then manually injects OpenXML drawing elements (w:drawing/wp:inline/a:graphic/a:graphicData/pic:pic) as a simplified placeholder for an embedded object. It generates an OLE stream consisting of a small header plus a user-supplied CLSID (little-endian UUID bytes), pads it to 512 bytes, and writes it to embedded_ole.bin. The script explicitly notes that python-docx does not directly support embedding OLE binary parts, and suggests manual embedding via external tools. - README.md: High-level description of the alleged Office zero-day/bypass, affected Office versions, and testing guidance (open in an unpatched Office VM; monitor CLSID registry lookups; suggests using oletools/OleViewDotNet and mentions kill-bit mitigations). - requirements.txt: python-docx, olefile, urllib3 (urllib3 is imported but not used for network activity in the script). Exploit capabilities: - Generates a test DOCX and a standalone OLE stream file to support research into OLE handling/bypass behavior. - Requires user interaction (opening the document in Office). No preview-pane vector. - Does not include a working embedded OLE part inside the DOCX (only a placeholder XML structure) and does not include a real malicious payload (no shellcode/VBA/command execution logic). Notable code concern: - The function generate_ole_stream() calls check_vuln() which invokes subprocess.Popen([p, u], shell=True) using two obfuscated strings. This behavior is unrelated to DOCX/OLE generation and could be suspicious or simply non-functional; it does not clearly implement exploitation but does represent an unexpected process-spawn attempt.nicole2ilodl · Disclosed Jan 27, 2026 · python · user-assisted / client-side (malicious Office document with embedded OLE object)PoCCVE-2026-21509-POCThis repository is a small proof-of-concept exploit generator consisting of one Python script and a minimal README. The main file, CVE-2026-21509.py, creates a crafted DOCX document intended to trigger CVE-2026-21509 in Microsoft Office/Word by embedding a valid OLE compound file inside the Office Open XML package. The exploit does not perform exploitation over the network and contains no reverse shell, downloader, or post-exploitation payload. Its core capability is file generation: it decodes a hardcoded minimal OLE template, patches a 16-byte CLSID placeholder at offset 0x80 using a user-provided or default COM CLSID, and then assembles a complete DOCX structure in a temporary directory before zipping it into the final output document. Repository structure is straightforward: - README.md: brief description only. - CVE-2026-21509.py: full exploit logic and CLI entry point. Within the Python script, the main functional components are: - patch_ole_clsid(): parses a CLSID string with Python's uuid module and inserts the little-endian CLSID bytes into the embedded OLE template. - create_malicious_docx(): builds the Office document structure, including required directories, OLE binary placement, content types, relationship files, document properties, and the main Word XML that references the embedded object. - __main__ block: exposes command-line options for output filename and CLSID. The exploit is best classified as a POC rather than an operational weapon. It demonstrates document construction needed to exercise the vulnerability, but it does not include a secondary payload or automated delivery. The attack vector is a malicious file that must be opened in a vulnerable Office environment, likely on Windows due to COM/OLE CLSID usage. No external URLs, IPs, domains, or C2 infrastructure are present in the code; the only fingerprintable artifacts are the internal DOCX package paths and the default CLSID value.DameDode · Disclosed Mar 12, 2026 · python · markdown · local · filePoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft Corporation365 Appsapplication
Microsoft CorporationMicrosoft Officeapplication
Microsoft CorporationOffice 2016application
Microsoft CorporationOffice 2019application
Microsoft CorporationOffice Long Term Servicing Channelapplication
FAQ

Frequently asked questions

Is CVE-2026-21509 exploited in the wild?
Yes. As of Nov 13, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jan 26, 2026.
Is there a public exploit for CVE-2026-21509?
Yes. Mallory tracks 5 public exploits or proofs of concept for CVE-2026-21509, the earliest disclosed Jan 27, 2026.
Is there a patch for CVE-2026-21509?
Install Microsoft's applicable security updates for the exact Office edition and servicing channel, beginning with the emergency updates released January 26, 2026. Identified minimum fixed versions include 16.0.5539.1001 for Office 2016 and 16.0.10417.20095 for Office 2019.
What products are affected by CVE-2026-21509?
Microsoft Corporation 365 Apps, Microsoft Corporation Microsoft Office, Microsoft Corporation Office 2016, Microsoft Corporation Office 2019, and Microsoft Corporation Office Long Term Servicing Channel.
How severe is CVE-2026-21509?
CVE-2026-21509 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 70.8% (99th percentile) as of Nov 13, 2026.
Activity feed

Recent activity

522 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+51 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence68Every report linking this CVE to a named adversary.
Associated malware82Malware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity144Community discussion across Reddit, Mastodon, and other social sources.