Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRun unprivileged local app on device
-
DeliveryDeliver crafted ZIP to privileged parser
-
ExploitTrigger heap overflow in getEntryFileName
-
ExecutionCorrupt heap in privileged context
-
ImpactEscalate privilege locally
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap 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 LOCAL access (AV:L): the attacker must already be able to run code on the device, typically via an installed or compromised unprivileged app, which then drives a privileged component to parse attacker-controlled data through getEntryFileName in ZipFileRO.cpp (the ZIP central-directory entry-name read path). No elevated privileges (PR:N) and no user interaction (UI:N) are needed once local code execution exists. The precise malformed input that triggers the overflow is not detailed in the available sources. Limiting factors: the vulnerability is not remotely reachable, requires prior local execution, and affects only Android versions 14 through 17; devices patched per the 2026-11-01 Android Security Bulletin are not affected. |
| Impact | This is a locally-exploitable heap buffer overflow (CWE-122) in Android's native ZipFileRO.cpp. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.4 HIGH) is internally consistent with the description: the attack vector is LOCAL (not network), complexity is low, no privileges are required per Google's bulletin convention ('no additional execution privileges needed'), and impact is full C/I/A compromise within an unchanged scope - i.e. local privilege escalation. The exploitation signals, however, are modest: EPSS is 0.12% (2nd percentile), there is no CISA KEV listing, and no public exploit or PoC reference is present in the supplied data, so the status is no public exploit identified at time of analysis. The vuln.today decision label is 'this_week' (not act_now/emergency), aligning with a real-but-not-urgent priority. The key tension is high CVSS severity (8.4) versus very low real-world exploitation probability (EPSS 2nd percentile, no KEV): this reflects a serious memory-safety defect whose exploitation requires local code execution first, which tempers the practical risk relative to the raw score. Note the LOCAL vector means this is not remotely reachable despite PR:N; the 'unauthenticated' reading of PR:N here means no elevated privileges, not network-remote access. |
| Exploit ScenarioDerived | A malicious or compromised low-privilege application already present on the device causes a privileged Android component to parse a crafted ZIP archive via ZipFileRO, triggering a heap buffer overflow in getEntryFileName and corrupting adjacent heap memory. No user interaction is required. If the overflow is shaped into reliable control-flow or data corruption, the attacker gains code execution in a higher-privileged context, escalating privilege; no public exploit code is identified in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Local privilege escalation in Google Android 14, 15, 16, 16-QPR2 and 17: a heap buffer overflow (CWE-122) in getEntryFileName in ZipFileRO.cpp, the native ZIP central-directory entry-name read path, can be driven by an attacker who already has local code execution on the device - typically an installed unprivileged app - to corrupt heap memory and gain code execution in the context of the privileged component that parses the archive, with no additional execution privileges and no user interaction required (CVSS 8.4, AV:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The flaw is not remotely reachable and its exploitation prerequisite is prior local execution; the exact malformed ZIP input that triggers the overflow is not detailed in the available sources. EPSS is low at 0.12% (2nd percentile) and no public exploit has been identified at time of analysis, but the vendor has published a fix in the 2026-11-01 Android Security Bulletin, and the priority assessment places remediation in the current week.
RemediationAI
Apply the Android security fixes published in the 2026-11-01 Android Security Bulletin (https://source.android.com/docs/security/bulletin/2026/2026-11-01), which is the vendor-released patch for this issue; the supplied data does not list specific build or patch identifiers, so consult the bulletin for the exact build numbers per device branch. Because exploitation requires prior local code execution by an unprivileged app, the practical compensating control is to constrain what code can run before patching: restrict installation of apps from untrusted sources and audit sideloaded or enterprise-distributed applications, at the cost of reduced user and deployment flexibility, and treat any app that parses untrusted ZIP or APK content as a potential delivery vector for the malformed archive the parser mishandles. Keeping the platform at a patch level at or after the 2026-11-01 bulletin is the only complete fix; no alternative workaround that removes the vulnerable parsing path is described in the available sources.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ZipFileRO.cpp is part of Android's native ZIP handling code (libziparchive), which parses the ZIP central directory and resolves entry names through getEntryFileName. The weakness class is CWE-122, a heap-based buffer overflow: a length or size derived from archive metadata is used to read or copy entry-name data into a heap allocation without adequate bounds validation, so an archive crafted with an inconsistent entry-name length can write past the end of that buffer. Android's CVSS vector confirms the local attack vector (AV:L) with no privileges (PR:N) and no user interaction (UI:N), meaning the overflow is reachable once any code is executing on the device and can hand attacker-controlled archive data to the vulnerable parser. The sources do not specify which system component performs that parsing, whether the issue is a read or a write past the allocation, or what precise malformed-input condition triggers it; those details are not described in the available evidence.
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:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Local vector requiring on-device code execution (AV:L) but no elevated privileges or interaction (PR:N/UI:N); heap overflow yields full code execution, so C:H/I:H/A:H, scope unchanged.
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In getEntryFileName of ZipFileRO.cpp, there is a possible memory safety issue due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Executive ViewAI
A high-severity local privilege escalation vulnerability in Google Android's ZIP parsing component (CVE-2026-58995) could allow a malicious app already installed on a device to gain elevated privileges within the privileged component that processes ZIP archives. This impacts the entire fleet of Android 14, 15, 16, 16-QPR2, and 17 devices used across the organization, potentially exposing sensitive data and enabling further compromise. Given the low exploitation likelihood but high potential impact, leadership should prioritize patching to maintain device integrity and protect corporate assets.
Vendor-released patch: 2026-11-01 Android Security Bulletin
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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 heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
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-115420
GHSA-v548-xc8v-gcmr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB