Security readout for executives and security teams
Plain-English summary
A flaw in Microsoft 365 Word Copilot could let an unauthenticated network attacker expose sensitive information when a user interacts with malicious content. The vulnerability affects confidentiality rather than data integrity or service availability. The available sources do not identify affected versions or confirm exploitation.
Executive priority
Treat this as a high-priority confidentiality risk. Quickly establish whether Word Copilot is enabled, verify Microsoft's remediation status, and reduce interaction with untrusted documents. Emergency incident response is not supported by current exploitation evidence.
Technical view
CVE-2026-21521 is a CWE-150 control-sequence neutralization flaw in Word Copilot. It is network-accessible, requires no privileges, and requires user interaction. Its CVSS 3.1 score is 7.4, with changed scope and high confidentiality impact but no stated integrity or availability impact.
Likely exposure
Organizations using Microsoft 365 Word Copilot may be exposed, but the supplied record provides no affected-version boundaries. Prioritize environments where Copilot processes documents or content received from external or untrusted sources.
Exploitation context
The source bundle does not report active exploitation and marks the CVE as absent from KEV. Exploitation requires user interaction, but no authentication and low attack complexity increase practical risk. No exploit mechanics should be inferred from the limited public description.
Researcher notes
The record establishes CWE-150, network reachability, no privileges, required user interaction, changed scope, and high confidentiality impact. It does not provide affected versions, technical root-cause detail, indicators, or confirmed exploitation. Validation should remain defensive and vendor-guided.
Mitigation direction
Review Microsoft's advisory for affected service states and official remediation guidance.
Confirm Microsoft 365 and Word Copilot updates or service-side protections are applied.
Limit Copilot processing of untrusted documents until remediation status is verified.
Reinforce caution around unexpected documents requesting Word or Copilot interaction.
Validation and detection
Inventory tenants and users with Microsoft 365 Word Copilot enabled.
Compare deployed or service-reported status with Microsoft's advisory.
Verify remediation through Microsoft 365 administration and update reporting.
Review security telemetry for suspicious Word Copilot interactions involving untrusted content.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-150: 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-150 · source CWE mapping
Improper Neutralization of Escape, Meta, or Control Sequences
Improper Neutralization of Escape, Meta, or Control Sequences represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.