Actively exploited vulnerability

Microsoft Office: security bypass flaw under attack

CVE-2026-21509 · Microsoft Office Security Feature Bypass Vulnerability

Concerns everyone who uses it7.8 high

What is affected

Microsoft Office is found on ordinary personal computers and phones, so this is not only a problem for companies. If you use it and have not updated since the fix was released, you are exposed.

Microsoft Office contains a security feature bypass vulnerability in which reliance on untrusted inputs in a security decision in Microsoft Office could allow an unauthorized attacker to bypass a security feature locally. Some of the impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.

CISA's description

What an attacker can do

This is a security bypass flaw. It lets an attacker slip past a built-in protection, so warnings and checks that normally stop malicious content never appear.

How it is reached
Needs access to the device or a file opened on it
Access the attacker needs
No account needed
Does the victim have to do something?
Yes, the victim must open or click something

What to do

  1. Update Microsoft Office now. Open the update or "About" screen, install whatever is offered and restart the app or device, because the fix is not active until you do.
  2. Turn on automatic updates so the next fix arrives without you having to look for it.
  3. If your device is too old to receive this update, stop using the affected app for anything sensitive and plan a replacement.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Action required by CISA for US federal agencies

Vendor advisories and fixes

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on January 26, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by February 16, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 71% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 99.4% of all scored vulnerabilities.

Its CVSS severity score is 7.8 out of 10 (high), as recorded in the US National Vulnerability Database.

Technical description

Reliance on untrusted inputs in a security decision in Microsoft Office allows an unauthorized attacker to bypass a security feature locally.

NIST National Vulnerability Database
5,442 members already hereReading, writing, commenting and voting. 0 verified · 167 joined this year