Security readout for executives and security teams
Plain-English summary
A memory-handling flaw in Microsoft Word can let an attacker run code on an affected system after user interaction. Successful exploitation could expose data, alter information, or disrupt the device. The supplied evidence rates it 7.8 High, but does not establish active exploitation.
Executive priority
Treat this as a high-priority patching issue because compromise could have full confidentiality, integrity, and availability impact. Required user interaction and no confirmed exploitation reduce immediate emergency pressure, but do not justify delay. Track remediation to completion across both user endpoints and listed SharePoint servers.
Technical view
CVE-2026-20948 is a CWE-822 untrusted pointer dereference vulnerability. Its CVSS 3.1 vector indicates local access, low complexity, no privileges, required user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. The exact delivery mechanism is not detailed in the supplied sources.
Likely exposure
Potential exposure includes Microsoft 365 Apps for Enterprise, Office 2019, Office LTSC 2021 and 2024, their listed Mac editions, Word 2016, and the listed SharePoint 2016 and 2019 products. Confirm exact builds and applicability through Microsoft because the supplied version identifiers may not uniquely establish patch status.
Exploitation context
The record is not listed in KEV, and the CVSS exploit-maturity value is unproven. No supplied source confirms active exploitation or a public exploit. Exploitation requires user interaction, but the sources do not describe the required content, delivery channel, or observable indicators.
Researcher notes
The supplied vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C. This supports an official remediation and unproven exploit maturity, but the bundle lacks build-specific update identifiers, technical root-cause detail, indicators, and exploit confirmation. Use Microsoft guidance for precise applicability.
Mitigation direction
- Inventory every listed Microsoft Office, Word, and SharePoint product across managed systems.
- Apply the applicable security updates identified in Microsoft's CVE advisory after compatibility testing.
- Follow deployment prerequisites or additional mitigations documented in current Microsoft guidance.
- Prioritize systems whose users routinely handle untrusted or externally supplied documents.
Validation and detection
- Compare installed product editions and versions against Microsoft's CVE advisory.
- Confirm applicable Microsoft security updates are installed on every identified system.
- Re-scan managed assets and investigate any affected or unverifiable installation.
- Review telemetry for anomalous code execution associated with Word; supplied evidence provides no specific indicators.
- Verify the listed SharePoint servers were included in exposure assessment and remediation.
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-822: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-20948 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
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/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.
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:U/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:U/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.
- 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 Word Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
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.
Untrusted Pointer Dereference
Untrusted Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.