Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted PPT via email/link
-
DeliveryVictim opens file in Office
-
ExploitTrigger out-of-bounds read in parser
-
ExecutionLeak adjacent process memory
-
ImpactExfiltrate disclosed data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to open a specially crafted PowerPoint file (UI:R) in a vulnerable Office build - one of Microsoft 365 Apps for Enterprise, Office 365 for Mac, Office LTSC 2021/2024, or Office LTSC for Mac 2021/2024 per the CPE list. No authentication or elevated privileges are needed (PR:N), and no special non-default Office configuration is indicated by the data. The primary limiting factor is the mandatory user interaction: the attack fails unless a user is socially engineered into opening the malicious presentation, and Protected View / Mark-of-the-Web sandboxing on files from untrusted sources further constrains realistic exploitation. |
| Impact | This is a moderate-severity information disclosure flaw (CVSS 6.5) in Microsoft Office PowerPoint rooted in CWE-125 (out-of-bounds read). The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N indicates that although the attack vector is network, successful exploitation REQUIRES user interaction (UI:R) - the victim must open a malicious presentation file - which materially lowers real-world risk compared to a zero-click network flaw. Privileges are not required (PR:N, unauthenticated) and complexity is low (AC:L), but the user-interaction gate means this is not wormable or automatable. Impact is confined to confidentiality (C:H / I:N / A:N): it can leak memory contents (potentially useful for defeating ASLR or harvesting sensitive data) but cannot by itself modify data or crash the application. No EPSS score, KEV listing, or public exploit was provided in the input; there is no public exploit identified at time of analysis and no evidence of active exploitation, so this reads as a real-but-not-urgent patch priority rather than an emergency. The 'Buffer Overflow' tag is slightly imprecise - CWE-125 is an out-of-bounds READ (over-read / disclosure), not a classic out-of-bounds write - which is consistent with the confidentiality-only impact. All signals are internally consistent; no conflicting data was observed. |
| Exploit ScenarioDerived | An attacker crafts a malicious PowerPoint presentation that triggers an out-of-bounds read when parsed, then delivers it to a victim via email or a download link. When the victim opens the file in a vulnerable Office build, the flaw leaks adjacent process memory back to attacker-controlled content, exposing sensitive data or information useful for bypassing memory protections. No public proof-of-concept was provided in the input, and exploitation depends entirely on the user opening the crafted file (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
An out-of-bounds memory read in Microsoft PowerPoint lets remote attackers leak information from the memory of the affected Office process when a user opens a specially crafted presentation file. The flaw carries a CVSS 3.1 base score of 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), meaning confidentiality is heavily impacted while integrity and availability are untouched, and it affects Microsoft 365 Apps for Enterprise, Office 365 for Mac, and Office LTSC 2021/2024 on both Windows and macOS. No public exploit has been identified at time of analysis, but the attack path is straightforward: an unauthenticated attacker only needs to convince a victim to open a malicious .ppt/.pptx file, so email and web-delivered documents remain the primary delivery vector. A vendor patch is available through Microsoft's update guide.
RemediationAI
Patch available per vendor advisory: Microsoft has released an update for CVE-2026-108455, and the definitive list of fixed builds per product and channel is published in the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-108455 - apply the latest Office update for your channel (Current Channel, Monthly Enterprise Channel, or LTSC) on every affected Windows and macOS installation. Until updates are deployed everywhere, rely on compensating controls that specifically counter the required user-interaction step: keep Protected View and Application Guard for Office enabled for files originating from the internet or email attachments, which prevents the malicious presentation from being parsed by the full Office engine at all (trade-off: legitimately downloaded documents open in a restricted, read-only viewer until the user explicitly trusts them); ensure Mark-of-the-Web tagging is preserved through email and browser download paths, since stripping it silently disables that protection; and strip or quarantine legacy PowerPoint formats (.ppt, .pps) and untrusted .pptx attachments at the mail gateway and web proxy, accepting the operational cost that some business documents will require an explicit release request. Additional hardening with limited downside includes disabling ActiveX and macro execution in PowerPoint, which does not remove this parsing flaw but reduces the chance a leaked memory value is combined with a second-stage primitive in a chained attack. There is no configuration change that fully eliminates exposure - updating Office remains the only complete fix.
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 vulnerability is classified as CWE-125 (Out-of-bounds Read), a memory-safety class in which the software reads past the end of an allocated buffer. In Office document parsers this typically occurs while interpreting malformed structures inside the PowerPoint binary or OOXML container format - for example a length or offset field that does not match the actual data present - causing the parser to copy adjacent heap contents into attacker-observable output. Because the CVSS impact vector is C:H/I:N/A:N, the practical consequence is a memory-disclosure primitive rather than code execution: leaked heap bytes may reveal pointer values or other process state that could later be used to defeat ASLR in a chained exploit, but the vulnerability itself does not corrupt memory or crash the parser. The CPE inventory confirms this is a cross-platform client issue spanning Microsoft 365 Apps for Enterprise, Microsoft Office 365 for Mac, Office LTSC 2021 and 2024, and Office LTSC for Mac 2021 and 2024, all of which share parsing code. Note that the CVSS vector carries PR:N, so no authentication or special privileges are required, and UI:R confirms the decisive prerequisite is user interaction - the victim must open the crafted file - which is also why Protected View and Mark-of-the-Web defenses materially reduce exposure.
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 delivered remotely (AV:N) but requires the user to open it (UI:R); no auth needed (PR:N); CWE-125 over-read leaks memory so C:H with no 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-102467
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB