Skip to content
Server Security Center
KEVhigh7.8

CVE-2026-21509: Microsoft Office Security Feature Bypass

Microsoft Office · listed in the CISA catalog of actively exploited vulnerabilities since 2026-01-26.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
71%
higher than 99.4% of all CVEs
Added to CISA KEV
2026-01-26
US federal due date 2026-02-16
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-21509 explained

CVE-2026-21509 is a security feature bypass in Microsoft Office caused by reliance on untrusted inputs in a security decision (CWE-807). An unauthorized attacker can bypass a security feature locally. CISA lists it as known exploited, so affected Office installations should be updated with priority.

Impact

A successful attack can lead to high impact on confidentiality, integrity and availability. CISA rates the technical impact as total. The attack is local, needs low complexity and no privileges, but requires user interaction, such as a user opening content. CISA judges it not automatable, so attacks need manual steps per target. Attackers are known to exploit it. Ransomware use is listed as unknown.

Who is affected

The CVE record lists Microsoft Office 2016 builds before 16.0.5539.1001 (fixed in 16.0.5539.1001) and Microsoft Office 2019 builds before 16.0.10417.20095 (fixed in 16.0.10417.20095), both 32-bit and x64. Microsoft 365 Apps for Enterprise, Microsoft Office LTSC 2021 and Microsoft Office LTSC 2024 are affected in builds before the fixed release. For these, the record names no fixed version and refers to the vendor release notes.

Written with AI from the data on this page and checked against it automatically.

Official description

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

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

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft 365 Apps for Enterprise32-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in
  • Microsoft Office 201632-bit, x64
    Affected
    • < 16.0.5539.1001
    Fixed in
    • 16.0.5539.1001
  • Microsoft Office 201932-bit, x64
    Affected
    • < 16.0.10417.20095
    Fixed in
    • 16.0.10417.20095
  • Microsoft Office LTSC 202132-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in
  • Microsoft Office LTSC 202432-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Office 2016: 16.0.5539.1001
    • Microsoft Office 2019: 16.0.10417.20095
    For the other affected products the CVE record names no fixed version – see the table and the vendor advisory.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21509
  • CISA's deadline for US federal agencies: 2026-02-16 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Update Microsoft Office 2016 to 16.0.5539.1001 or later.
  2. Update Microsoft Office 2019 to 16.0.10417.20095 or later.
  3. Update Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024 to the fixed build named in Microsoft's advisory and release notes.
  4. Apply any mitigations in Microsoft's advisory where updates cannot be deployed right away.
  5. Warn users about opening untrusted files, since exploitation requires user interaction.
  6. Check endpoints for signs of compromise, as the vulnerability is known to be exploited.

For Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024 the CVE record names no fixed version. Check Microsoft's advisory and release notes for the fixed build and deploy it. Per CISA's required action, apply the vendor's mitigations, follow BOD 22-01 guidance for cloud services, or discontinue use if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-807 Reliance on Untrusted Inputs in a Security Decision

Questions about CVE-2026-21509

Is CVE-2026-21509 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-01-26, with a US federal due date of 2026-02-16. Whether it is used in ransomware campaigns is listed as unknown.
Can it be exploited remotely without user action?
The CVSS vector rates the attack as local and requiring user interaction, with no privileges needed. CISA rates it as not automatable.
Which version fixes my Office installation?
Office 2016 is fixed in 16.0.5539.1001 and Office 2019 in 16.0.10417.20095. For Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024, the record points to the vendor release notes for the fixed build.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.