Security readout for executives and security teams
Plain-English summary
CVE-2026-21509 is a Microsoft Office security feature bypass. An attacker can abuse how Office trusts input during a security decision. Exploitation requires local interaction and user involvement, but CISA KEV listing indicates known exploitation. Organizations using affected Office versions should treat this as urgent endpoint patching work.
Executive priority
High priority. This is not just theoretical because CISA lists it as known exploited. Patch Office endpoints promptly, starting with internet-facing users, executives, finance, legal, and other high-risk document-handling groups.
Technical view
The vulnerability is CWE-807: reliance on untrusted inputs in a security decision. Microsoft rates it CVSS 7.8 with local attack vector, low complexity, no privileges required, and required user interaction. Impact is rated high for confidentiality, integrity, and availability. Affected products include Microsoft 365 Apps for Enterprise and Office 2016, 2019, LTSC 2021, and LTSC 2024.
Likely exposure
Exposure is likely on Windows endpoints running the listed Microsoft Office products, especially unmanaged laptops, delayed update rings, or legacy Office deployments. The source bundle does not identify specific platforms, builds, or configurations beyond the affected product/version entries.
Exploitation context
CISA KEV presence supports known exploitation. The CVSS vector indicates exploitation is local and requires user interaction, so email, document-handling, or social-engineering paths may be relevant, but the provided sources do not describe a specific attack chain.
Researcher notes
Evidence is limited to the CVE description, CVSS, affected product list, MSRC advisory, CISA KEV reference, and Vicarius detection/mitigation pages. Do not assume exploit mechanics beyond local attack vector and user interaction. Validate exact fixed builds through Microsoft’s advisory.
Mitigation direction
- Apply Microsoft guidance and security updates from the MSRC advisory.
- Prioritize endpoints with affected Office versions and delayed update policies.
- Review Vicarius mitigation guidance if your organization uses those scripts.
- Harden document-handling controls pending full patch deployment.
Validation and detection
- Inventory Office versions across managed and unmanaged endpoints.
- Confirm Microsoft Office updates are installed according to MSRC guidance.
- Check CISA KEV tracking for remediation deadlines and status.
- Use approved detection tooling to identify remaining affected installations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-807: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-21509 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Office Security Feature Bypass VulnerabilityCVE reference, microsoft · vendor-advisory, patch
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-21509CVE reference, CISA-ADP · government-resource
- https://www.vicarius.io/vsociety/posts/cve-2026-21509-detection-script-microsoft-office-security-feature-bypass-vulnerabilityCVE reference, CVE
- https://www.vicarius.io/vsociety/posts/cve-2026-21509-mitigation-script-microsoft-office-security-feature-bypass-vulnerabilityCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Reliance on Untrusted Inputs in a Security Decision
Reliance on Untrusted Inputs in a Security Decision represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.