Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted PPT via email
-
DeliveryUser opens malicious presentation
-
ExploitTrigger out-of-bounds buffer read in parser
-
ExecutionLeak adjacent process memory
-
ImpactExfiltrate disclosed data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer over-read prevention
|
| Exploitation Conditions | Exploitation requires the victim to open a maliciously crafted PowerPoint file in a vulnerable build of Microsoft 365 Apps for Enterprise, Office LTSC 2021/2024, or the corresponding macOS Office editions (Office 365 for Mac, Office LTSC for Mac 2021/2024). No authentication is required of the attacker (PR:N), and no special product configuration is needed - default PowerPoint file-parsing behavior is sufficient. The principal limiting factor is mandatory user interaction (UI:R): the attack cannot proceed unless a user is socially engineered into opening the attacker-supplied document, and Protected View / Mark-of-the-Web handling for files from untrusted sources can further blunt automatic exploitation. Impact is confined to confidentiality (memory disclosure); there is no integrity or availability effect from this flaw alone. |
| Impact | This is a moderate-priority confidentiality issue rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, base 6.5) indicates a remotely-deliverable, unauthenticated, low-complexity flaw whose single mitigating factor is required user interaction (UI:R) - the victim must open a malicious PowerPoint file. CWE-126 (buffer over-read) combined with C:H/I:N/A:N is consistent with a memory-disclosure bug: the attacker reads adjacent process memory (potentially leaking heap contents, addresses useful for ASLR bypass, or document data) but cannot modify data or crash/deny service through this metric set. No EPSS score, SSVC decision, KEV listing, or POC indicator was provided in the input; per CISA KEV absence and no POC signal, there is no public exploit identified at time of analysis. The practical risk is therefore social-engineering-bound: unlike a wormable network bug, exploitation requires luring a user to open a crafted file, which places this below actively-exploited Office RCE chains in urgency. No conflicting signals were detected between the CVSS vector and the description - both point to a remote, user-interaction-gated information disclosure. A patch is available from Microsoft, so remediation is straightforward. |
| Exploit ScenarioDerived | An attacker crafts a malicious PowerPoint presentation that triggers an out-of-bounds buffer read when parsed, then emails or shares it with a target. When the victim opens the file in a vulnerable Office/PowerPoint build, the flaw leaks adjacent process memory back to attacker-controlled content, potentially exposing sensitive in-memory data or address-layout information useful for chaining further exploits. No public exploit code was identified at time of analysis, and successful exploitation depends entirely on the user opening the file. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
An information disclosure vulnerability in Microsoft PowerPoint allows a remote, unauthenticated attacker to trigger an out-of-bounds memory read by convincing a victim to open a specially crafted presentation file, potentially exposing heap contents that may contain sensitive data. Affected builds span Microsoft 365 Apps for Enterprise, Office 365 for Mac, and the Office LTSC 2021 and 2024 releases on both Windows and macOS. The attacker needs no credentials (PR:N), but the attack hinges entirely on user interaction (UI:R) - the document must be opened, and Protected View or Mark-of-the-Web handling for externally sourced files can interrupt the chain. Microsoft has released a vendor patch and no public exploit code or active exploitation has been identified at time of analysis.
RemediationAI
Apply the Microsoft-released fix as soon as possible; the vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-108454 provides the exact patched build numbers for Microsoft 365 Apps for Enterprise, Office 365 for Mac, Office LTSC 2021/2024, and Office LTSC for Mac 2021/2024 - Microsoft 365 Apps update through the standard update channel, while LTSC/volume-license installs require the corresponding monthly or security update package. Where patching cannot be immediate, compensating controls are effective because exploitation requires the user to open a hostile file: keep Protected View enabled for files originating from the internet and from untrusted locations, and do not weaken Mark-of-the-Web behavior, since both prevent the parser from being reached for externally sourced presentations; note that turning off MOTW propagation or Protected View to reduce prompt fatigue materially increases exposure and should be avoided. Additional friction can be added with mail-gateway and web-proxy attachment filtering that strips or sandboxes .ppt/.pptx files from external senders, plus endpoint policies that open Office documents from downloads and email attachments in a sandbox or Application Guard container - the trade-off being occasional compatibility issues and user friction with embedded content and macros. Blocking the PowerPoint file extensions outright is not a realistic enterprise control, so detection should be paired with monitoring for anomalous Office processes reading unusual memory regions or outbound connections following document opens.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 5 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-126 (Buffer Over-read): PowerPoint's document parser reads past the end of an allocated buffer while processing malformed presentation content, and the over-read bytes are surfaced back to the attacker as disclosed memory. Because only read operations are involved, the flaw produces no memory corruption, no code execution, and no integrity or availability impact - the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N reflects a confidentiality-only outcome with a mandatory user-interaction gate. The CPE data identifies the affected code bases as Microsoft 365 Apps for Enterprise, Microsoft Office 365 for Mac, Microsoft Office LTSC 2021 and 2024, and Microsoft Office LTSC for Mac 2021 and 2024, meaning the same PowerPoint parsing engine is shared across the subscription and perpetual-license Windows and macOS delivery channels. Because file parsing happens as soon as a document is rendered, exploitation does not require any non-default configuration, but it also cannot proceed without a user proactively opening the malicious file - which is why the supply-chain-style shortcut of drive-by rendering does not apply and why email/web-delivered lures remain the practical vector.
Know when Microsoft 365 Apps For Enterprise gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Malicious file is remotely delivered (AV:N) and reliably parsed (AC:L) with no attacker auth (PR:N), but the victim must open it (UI:R); a buffer over-read leaks memory (C:H) without integrity or availability impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.org
Microsoft Office PowerPoint Information Disclosure Vulnerability
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Local code execution in Microsoft Word (and Office/SharePoint components that render Word content) stems from an integer
Arbitrary code execution in Microsoft Office Word (and the broader Office/365/SharePoint family) arises from a stack-bas
Local code execution in Microsoft Word (part of Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, and Office for M
Arbitrary code execution in Microsoft PowerPoint (and the broader Microsoft Office/365 suite on Windows and macOS) arise
Local code execution in Microsoft Office PowerPoint (including Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, a
Local code execution in Microsoft Office PowerPoint (CWE-122 heap-based buffer overflow) lets an unauthorized attacker r
Local code execution in Microsoft Word (and the wider Microsoft Office / Microsoft 365 Apps family) lets an unauthorized
Local code execution in Microsoft Word (Office 2016/2019, Microsoft 365 Apps, Office LTSC 2021/2024) arises from a heap-
Local code execution in Microsoft Office Word (CWE-416 use-after-free) allows an unauthorized attacker to run arbitrary
Local code execution in Microsoft Office Word (Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Word 2016, and the macOS
Local code execution in Microsoft Office Word (via a stack-based buffer overflow, CWE-121) lets an attacker run arbitrar
Local code execution in Microsoft Office Word (across Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Office for Mac, an
EUVD-2026-102466
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB