Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Microsoft Office Security Feature Bypass (CVE-2026-21509)

CVE-2026-21509 is a Microsoft Office security feature bypass.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-21509
Vendor
Microsoft
Affected Product
Microsoft Office and Microsoft 365 Apps for Enterprise
Exploitation
Listed in CISA KEV
Published
2026-01-26

Microsoft says Office relied on untrusted input when making a security decision, which could let an unauthorized attacker bypass OLE protections.Microsoft rates the flaw Important, with a CVSS 3.1 base score of 7.8 and temporal score of 7.2. Neither the Microsoft record nor NVD gives a CVSS 4.0 score.

What it allows

How Does CVE-2026-21509 Bypass Office Protection?

Microsoft says the bypass affects OLE mitigations that protect Office users from vulnerable COM and OLE controls. An attacker must deliver a malicious Office file and persuade a user to open it. Microsoft explicitly excludes the Preview Pane as an attack path.

The public advisory does not identify a specific document format or a later payload. The security decision depends on untrusted input, but the record does not disclose more of the underlying implementation.

Teams can place this exploited flaw in a broader vulnerability intelligence platform workflow. The useful first distinction is whether an Office endpoint needs a security update or a restart to receive Microsoft's service-side protection.

Is CVE-2026-21509 Being Exploited?

Yes. Microsoft's January 26, 2026 advisory marked exploitation detected, and CISA added the CVE to its Known Exploited Vulnerabilities catalog that day. This is evidence of exploitation in January, not a new November attack claim.

On November 14, 2026, a GitHub repository search for CVE-2026-21509 returned 15 public matches. This search-result count does not establish how many working exploits or incidents exist.

What Should Set the Response Priority?

KEV inclusion and the required user action matter more than the 7.8 score alone. Brandefense Blackhole counted three dark chat posts mentioning this CVE from August 16 through November 14, 2026. These are post mentions, not confirmed attacks.

As a Brandefense precaution, correlate suspicious Office document opens with the affected build inventory and endpoint alerts. Keep that review separate from the patch check; an alert alone does not prove this CVE was used.

Who is affected

Which Office Editions Need a Patch or Restart?

Microsoft lists 32-bit and 64-bit Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, and Microsoft 365 Apps for Enterprise. Office 2016 needs build 16.0.5539.1001 or later. Office 2019 needs build 16.0.10417.20095 or later.

Microsoft says Microsoft 365 Apps and Office 2021 or later receive a service-side change, but users must restart Office applications for it to take effect. For those editions, the advisory points to Microsoft's Office security release history instead of one comparable fixed build number.

For Office 2016 and 2019, confirm the January 26 security update is installed. Open an Office application, select File, Account, then About, and compare the displayed build with the applicable Microsoft boundary. Use your patch management process to record both the installed build and the post-update check.

How Can Teams Verify Protection?

First, separate Office 2016 and 2019 endpoints from Microsoft 365 Apps and newer Office editions. Install the applicable security update on the older editions, then verify their running build. On the service-side group, close every Office application and reopen it after the change is available.

Microsoft's advisory contains conflicting older mitigation wording about registry keys and an upcoming update. Its later FAQ confirms the 2016 and 2019 updates were available on January 26, 2026. Follow the update and restart paths above rather than relying on those older lines.

Timeline

  1. 2026-01-26

    Microsoft published the advisory and updates for Office 2016 and 2019. CISA added the CVE to its Known Exploited Vulnerabilities catalog.

  2. 2026-01-29

    Microsoft updated its mitigation text; its revision history calls this an informational change.

What to do

  1. Inventory affected Office editions

    Identify 32-bit and 64-bit Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, and Microsoft 365 Apps for Enterprise endpoints.

  2. Update Office 2016 and 2019

    Install Microsoft's January 26, 2026 security update. Confirm Office 2016 reaches build 16.0.5539.1001 or later and Office 2019 reaches 16.0.10417.20095 or later.

  3. Restart newer Office applications

    For Microsoft 365 Apps and Office 2021 or later, close and reopen all Office applications so Microsoft's service-side protection takes effect.

  4. Check the running build and alerts

    In Office, use File, Account, About to read the build. As a Brandefense precaution, review suspicious document opens and endpoint alerts against the affected inventory.

What Brandefense can do

Frequently Asked Questions

Does CVE-2026-21509 require a user to open a file?

Yes. Microsoft says an attacker must send a malicious Office file and convince the user to open it. The Preview Pane is not an attack path.

Are Office 2016 and 2019 updates available?

Yes. Microsoft says both updates became available on January 26, 2026. Verify build 16.0.5539.1001 for Office 2016 or 16.0.10417.20095 for Office 2019.

Why must Microsoft 365 Apps users restart Office?

Microsoft says these users receive a service-side change automatically. Office applications must be restarted for that protection to take effect.

When was exploitation confirmed?

Microsoft marked exploitation detected in its January 26, 2026 advisory. CISA added the CVE to KEV on the same date.

Sources

  1. Microsoft Office Security Feature Bypass VulnerabilityMicrosoft Security Response Center
  2. CVE-2026-21509 recordMicrosoft CNA via CVE Program
  3. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →