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
- Please adhere to Microsoft’s recommended guidelines to address this vulnerability. Implement all final mitigations provided by the vendor for Office 2021, and apply the interim corresponding mitigations for Office 2016 and Office 2019 until the final patch becomes available. For more information please see: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21509
- nvd.nist.gov/vuln/detail/CVE-2026-21509
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft 365 Apps for Enterprise32-bit, x64
- Microsoft Office 201632-bit, x64AffectedFixed in
- < 16.0.5539.1001
- 16.0.5539.1001
- Microsoft Office 201932-bit, x64AffectedFixed in
- < 16.0.10417.20095
- 16.0.10417.20095
- Microsoft Office LTSC 202132-bit, x64
- Microsoft Office LTSC 202432-bit, x64
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft 365 Apps for Enterprise32-bit, x64 |
| vendor release notes |
| Microsoft Office 201632-bit, x64 |
|
|
| Microsoft Office 201932-bit, x64 |
|
|
| Microsoft Office LTSC 202132-bit, x64 |
| vendor release notes |
| Microsoft Office LTSC 202432-bit, x64 |
| vendor release notes |
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
- 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
- Update Microsoft Office 2016 to
16.0.5539.1001or later. - Update Microsoft Office 2019 to
16.0.10417.20095or later. - 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.
- Apply any mitigations in Microsoft's advisory where updates cannot be deployed right away.
- Warn users about opening untrusted files, since exploitation requires user interaction.
- 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.1001and Office 2019 in16.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
Trackers and catalogs
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.