Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted Office document to target
-
DeliveryUser opens file in vulnerable Office
-
ExploitTrigger stack buffer overflow in Graphics Component
-
ExecutionExecute attacker-controlled code
-
ImpactElevate privileges on device
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution 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 attacker-supplied content (a crafted document or graphics object) within Microsoft Office for Android, builds 16.0.1 up to but not including 16.0.20430.20000 - fixed builds are not affected. The CVSS vector's PR:L means the attacker needs a low-privileged/legitimate app context, and UI:R means the exploit cannot fire without the user actively opening or rendering the malicious file. These two factors - required user interaction and an existing low-privilege foothold, combined with the narrow platform (Android) and version window - are the principal limits on real-world exploitability and should temper the raw 8.0 score. |
| Impact | This is a credible mid-to-high priority issue but not a top-tier emergency based on current signals. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 8.0) indicates a network-reachable, low-complexity attack that nonetheless requires both low-level privileges (PR:L - an authenticated/legitimate app context) and user interaction (UI:R - the victim must act, typically open a crafted document). No EPSS score, CISA KEV listing, SSVC decision data, or POC indicator was supplied, so exploitation probability and automatability cannot be quantified from this input; the exploitation status is therefore 'no public exploit identified at time of analysis.' A notable cross-reference tension exists: the description names the 'Microsoft Graphics Component' (phrasing usually associated with the Windows GDI/graphics stack), yet the EUVD affected-product data scopes this strictly to Microsoft Office for Android (16.0.1 < 16.0.20430.20000) - verify the true affected surface with Microsoft, because it materially changes who is at risk. A memory-corruption EoP that requires user interaction and some existing foothold on an Android device is meaningfully harder to weaponize at scale than an unauthenticated server-side RCE, so despite the 8.0 score the realistic urgency is moderate: patch promptly but it is unlikely to be mass-exploited. |
| Exploit ScenarioDerived | An attacker crafts a malicious document or image with a malformed graphics structure and delivers it to a victim running a vulnerable Microsoft Office build on Android. When the user opens the file, the Graphics Component overflows a stack buffer (CWE-121), letting the attacker corrupt memory and elevate privileges beyond the app's intended sandbox. Because the CVSS vector specifies UI:R and PR:L, success depends on the victim opening attacker-supplied content from an already-legitimate app context; no public exploit code is identified at this time. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
A stack-based buffer overflow in the Microsoft Graphics Component, reachable through Microsoft Office for Android, lets an authenticated attacker who can place a crafted document or graphics object in front of a victim gain code execution in the context of the mobile app, with high impact to confidentiality, integrity, and availability. Only builds from 16.0.1 up to but not including 16.0.20430.20000 are affected, and exploitation requires user interaction - the victim must open or render the malicious file - which materially narrows the practical attack surface despite the 8.0 CVSS score. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified; the vendor has published an update-guide entry, so affected organizations should treat this as a credible mid-to-high priority patching item rather than a top-tier emergency.
RemediationAI
Patch status per the source data is 'Available from vendor': Microsoft's update guide for CVE-2026-85881 should be the reference of record. Because the vulnerable version range ends at 16.0.20430.20000, remediation is achieved by updating Microsoft Office for Android to build 16.0.20430.20000 or later via Google Play or managed app distribution; consumers cannot manually sideload the graphics component independently of the app. Where immediate update is not feasible, compensating controls should focus on the two preconditions the vector imposes: the user-interaction requirement means restricting the app's ability to open untrusted documents - for example, using Android work-profile or MDM app-configuration policies to disable document opening from untrusted sources, blocking attachment preview from third-party mail clients, and enforcing managed-open-in policies so documents only open in vetted locations. Reducing the attacker's low-privileged foothold (the PR:L requirement) by tightening which apps and accounts can invoke Office for Android, and by isolating Office in a work profile with limited shared storage, lowers the chance that a malicious file reaches the vulnerable parser with a live app context. These controls carry trade-offs: disabling attachment preview or restricting managed-open-in degrades usability for legitimate document workflows and may generate help-desk load, and they do not eliminate the flaw, only reduce exposure - so they should be treated as interim measures until every device is confirmed on a fixed build.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package 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-121, a stack-based buffer overflow, occurring in the Microsoft Graphics Component - the shared rendering/parsing library stack that Office for Android uses to decode images and graphics objects embedded in documents. A malformed graphics object causes a fixed-size stack buffer to be overrun, corrupting adjacent stack memory and potentially allowing the attacker to redirect execution. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H indicates the attack is network-delivered and low complexity, but requires the attacker to already hold a low-privileged/legitimate app context (PR:L) and requires the victim to perform a user action (UI:R), typically opening or previewing the crafted document. The scope is unchanged (S:U), meaning the compromise is confined to the vulnerable Office for Android application process and its data, rather than escaping to the underlying Android OS. The public description frames this as an elevation-of-privileges bug, while the assessed vector scores high on all three CIA dimensions, which is consistent with memory-corruption exploitation inside the graphics parsing path rather than a simple information leak.
Know when Android 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:L/UI:R/S:U/C:H/I:H/A:H
Crafted content is delivered over a network but requires the victim to open it (UI:R) from a low-privileged app context (PR:L); memory corruption yields full C/I/A impact with no scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Stack-based buffer overflow in Microsoft Graphics Component allows an authorized attacker to elevate privileges over a network.
Articles & Coverage 1
Executive ViewAI
Microsoft Office for Android is affected by a high-severity code execution vulnerability that could let an attacker run malicious code on a user's mobile device when a crafted document is opened. The flaw requires user interaction and no public exploit identified at time of analysis, but successful exploitation could expose or alter sensitive business data accessible to the app. Leadership should ensure mobile productivity users are prioritized for patching because the fix is already available.
Apply vendor patch.
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.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-99574
GHSA-j3pf-m8p7-cgjj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB