Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious low-privilege app
-
DeliveryInvoke privileged system component
-
ExploitTrigger confused-deputy permission bypass
-
ExecutionExecute action with elevated privileges
-
ImpactFull local privilege escalation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service Proxy/intermediary controls
|
| Exploitation Conditions | Exploitation requires a local attacker presence on the device - in practice an already-installed malicious or compromised application running on Android 17 - which then invokes a privileged system component that fails to validate the caller's permissions (the confused deputy). No user interaction is required (UI:N) and no additional execution privileges are needed beyond initial app installation. Limiting factors: the attack is strictly local (AV:L), so there is no remote network exploitation path; an attacker must first get code running on the device, and the flaw affects Android 17 specifically. The precise vulnerable components ('multiple locations') and the exact trigger conditions are not described in the available sources. |
| Impact | Signals are moderately consistent and point to a serious-but-not-emergency local flaw. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.4) describes a locally-exploitable confused-deputy (CWE-441) that yields total compromise of the affected component without user interaction, which aligns with the SSVC Technical Impact of 'total'. However, the risk signals that drive urgency are low: SSVC reports Exploitation 'none' and Automatable 'no', no CISA KEV listing is present, and no EPSS probability was supplied in the input - so there is no evidence of active or scalable exploitation. The vuln.today Decision label is 'this_week', consistent with a high-impact local privilege escalation that warrants prompt patching but is not flagged act_now or emergency. Note a tension worth flagging: the vector sets PR:N, yet real-world exploitation of an Android confused-deputy escalation typically requires a malicious or compromised app already present on the device (local attacker position via AV:L) - PR:N reflects that the vulnerable privileged component grants access without the attacker holding those privileges, not that the device is remotely reachable. No EPSS score and no public exploit reference are present in the data, so widespread-exploitation likelihood cannot be quantified from these sources. |
| Exploit ScenarioDerived | A malicious or compromised low-privilege app installed on an Android 17 device abuses a privileged system component that performs an action on the app's behalf without correctly checking the caller's permissions (confused deputy). Because no user interaction and no additional execution privileges are required, the app silently escalates to the privileges of the deputy component, gaining high confidentiality, integrity, and availability impact on the device. No public exploit identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
Local privilege escalation in Android 17 allows an app already installed on the device to bypass permission checks and gain elevated access by invoking a privileged system component that fails to validate the caller's identity. The CVSS 8.4 score reflects high confidentiality, integrity and availability impact with no user interaction required, but the attack surface is strictly local - an attacker must first get code running on the device, and no network path exists. Exploitation is not confirmed: no public exploit code or KEV listing was identified at time of analysis, CISA SSVC records exploitation as 'none' and automatable as 'no', while technical impact is rated total; no EPSS score was supplied in the source data.
RemediationAI
No exact fixed build number is given in the available data; remediation is keyed to the Android Security Bulletin dated 2026-11-01 (https://source.android.com/docs/security/bulletin/2026/2026-11-01), which is where the vendor publishes the patched builds and the associated security patch level for Android 17 - apply that bulletin's patch level or later. Because exploitation requires a malicious or compromised app already resident on the device, the practical exposure window is governed by what can be installed: restricting sideloading, enforcing Google Play Protect verification and keeping the installed application inventory tight reduces the chance an attacker obtains the initial local foothold, though none of these substitutes for the platform update. No workaround short of the vendor patch is identified in the supplied sources, and the flaw is not remotely reachable, so perimeter network controls have no bearing on it.
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
The root cause class is CWE-441, Confused Deputy: a component that holds a privilege the caller does not possess performs an action on the caller's behalf without verifying that the caller is entitled to it. In Android's architecture this pattern lives at the Binder IPC boundary, where ordinary sandboxed applications send transactions to privileged system services (frequently in system_server) that enforce signature- or system-level permissions before carrying out sensitive operations. The description states the bypass exists 'in multiple locations', so more than one privileged entry point is believed to be affected, but the specific services, permission strings and exact trigger conditions are not described in the available sources. The CVSS vector AV:L/AC:L/PR:N/UI:N indicates a local attack that needs no prior privileges and no user interaction, which describes severity and preconditions rather than the mechanism itself. EUVD scopes affected versions to Android 17, and the sole reference is the Android Security Bulletin of 2026-11-01.
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 confused-deputy escalation (AV:L) needing a malicious app but no extra privileges (PR:N) or interaction (UI:N); total device impact gives C/I/A:H.
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Articles & Coverage 2
Executive ViewAI
A high-severity local privilege escalation vulnerability (CVE-2026-58885) in Android 17 could allow a malicious app already installed on a device to bypass permission checks and gain elevated system access. This poses a significant risk to our mobile fleet, as a single compromised or user-installed app could lead to full device compromise, exposing sensitive corporate data and undermining device integrity. Leadership should prioritize patching and interim controls to protect organizational assets and maintain regulatory compliance.
No vendor-released patch identified at time of analysis. Interim mitigations include enforcing app allowlisting, disabling sideloading, restricting privileged system component access via MDM policies, and deploying mobile threat defense to detect exploitation attempts.
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.
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-115608
GHSA-4hrg-57vv-cg9w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB