CVE-2026-21260: Microsoft Outlook Spoofing Vulnerability
Exposure of sensitive information to an unauthorized actor in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing over a network.
Security readout for executives and security teams
Plain-English summary
A network-based attacker may obtain sensitive information from affected Microsoft Outlook, Office, Microsoft 365 Apps, or SharePoint products and use it for spoofing. No account or user interaction is required according to the CVSS vector. The supplied evidence does not explain what is spoofed or what information is exposed.
Executive priority
Treat this as a high-priority confidentiality risk. Promptly identify affected endpoints and SharePoint servers, then apply verified Microsoft updates. Escalate internet- or broadly network-reachable systems first. Emergency incident response is not justified solely by this bundle because active exploitation is not established.
Technical view
CVE-2026-21260 is a CWE-200 information-exposure vulnerability rated CVSS 7.5. The vector indicates remote, low-complexity, unauthenticated exploitation without user interaction, with high confidentiality impact but no rated integrity or availability impact. The supplied bundle identifies Outlook, Office, Microsoft 365 Apps, and SharePoint releases as affected.
Likely exposure
Exposure is most likely where the listed Microsoft products and versions are deployed and reachable through relevant network paths. The bundle does not provide affected build ranges, configuration prerequisites, or service-level exposure details, so asset owners must confirm applicability against Microsoft's advisory.
Exploitation context
The supplied record does not establish active exploitation, and the CVE is not identified as being in CISA KEV. CVSS reports an unproven exploit-code maturity value. These facts do not prove exploitation is impossible; they mean confirmed exploitation is unsupported by the provided evidence.
Researcher notes
The public bundle provides limited vulnerability mechanics and unexpectedly includes both client applications and SharePoint servers. Do not infer a shared vulnerable component or attack path without Microsoft confirmation. Validate exact builds, prerequisites, and fixes from the vendor advisory before testing or declaring exposure.
Mitigation direction
Review Microsoft's CVE advisory for affected builds and applicable security updates.
Apply Microsoft-provided updates using the organization's normal expedited patch process.
Prioritize network-reachable installations of the listed Outlook, Office, Microsoft 365 Apps, and SharePoint products.
Use Microsoft guidance for any compensating controls if immediate updating is unavailable.
Validation and detection
Inventory deployments of every product and version listed in the CVE record.
Compare installed build numbers with Microsoft's current affected and remediated build information.
Verify applicable Microsoft security updates installed successfully across endpoints and servers.
Re-scan patched assets and investigate update failures or unmanaged installations.
Monitor security tooling for suspicious information-access or spoofing-related activity without assuming a known signature exists.
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 · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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.