Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRun low-privileged app on device
-
DeliveryInvoke flawed permission check
-
ExploitTrigger logic-error bypass
-
ExecutionEscalate to elevated privileges
-
ImpactAccess protected data/components
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
|
| Exploitation Conditions | Requires the attacker to already have local code execution at User (non-privileged app) level on an affected Google Android/Pixel device - i.e. a malicious or compromised app running on the device. No user interaction is needed once the app runs (UI:N), and no elevated privileges are required beyond normal app execution (PR:L). Limiting factors: the attacker must first get code onto the device (no remote/network vector, AV:L), and the device must be an unpatched version predating the 2026-09-01 Android/Pixel security bulletin fix. The generic description ('multiple locations', logic error in a permission check) means the precise triggering feature or configuration is not specified in the available data. |
| Impact | The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 High) is internally consistent with the description: a logic error causing a permission bypass that yields local privilege escalation requiring only existing User-level execution privileges and no user interaction. This is a genuine local privilege-escalation class issue, but the exploitation signals point to LOW real-world urgency: EPSS is only 0.13% (3rd percentile), there is no CISA KEV listing, and no public exploit code was identified in the provided data. The high base score is driven entirely by the C:H/I:H/A:H impact of a full permission bypass, not by ease of remote reach - the AV:L attack vector means an attacker must already be able to run code on the device (e.g. a malicious or compromised app). SSVC-style reading: exploitation status is 'none/POC-absent', automatable is unlikely given the local vector and need for an on-device foothold, and technical impact is 'total' for the escalated process. Net: a real patch-worthy local EoP, but not an emergency - priority should follow normal Android/Pixel monthly-bulletin patch cadence rather than out-of-band response. Note the description is generic ('multiple locations', 'logic error') so the exact affected component is not pinned down in the provided data. |
| Exploit ScenarioDerived | A user installs or is tricked into running a low-privileged malicious application on an affected Android/Pixel device. The app exploits the permission-bypass logic error to gain elevated privileges without any user interaction or additional prompts, escalating from an untrusted app context toward system/privileged access. No public exploit code was identified at time of analysis, so this would require attacker-developed tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
Local privilege escalation in Google Android/Pixel devices allows an already-running non-privileged app to bypass permission checks and gain elevated privileges through a logic error in the code. Exploitation requires the attacker to have existing local code execution at User level on an unpatched device, with no user interaction needed once the malicious or compromised app is running. No public exploit code or active exploitation is identified at time of analysis, and EPSS is low at 0.13% (percentile 3%).
RemediationAI
Apply the vendor fix from the 2026-09-01 Android/Pixel security bulletin at https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01; this is a vendor-released patch per the referenced advisory, though an exact Android build or kernel version is not specified in the input data. Because exploitation requires a malicious or compromised app already running at User level, reduce exposure by installing only trusted applications, disabling side-loading or unknown sources where feasible, and using managed-device policies to control app installation; these controls lower the chance an attacker obtains the required local app execution but do not fix the underlying permission bypass and may restrict legitimate app deployment. If immediate update is not possible, avoid granting sensitive permissions to untrusted apps and monitor for unexpected privilege changes, treating these as compensating measures rather than a full remediation.
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 vulnerability is classified as CWE-693, Protection Mechanism Failure, meaning the flaw is not a memory-safety issue but an incorrectly implemented or incomplete permission check in Android platform code. Android enforces application isolation through UIDs and permission mediation across user-space and kernel components; a logic error in multiple locations can permit a User-level app to reach protected functionality or data that should require higher privilege. The CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:* identifies Google Android as the affected product family, and EUVD lists the affected version set as 'Android Android kernel'. The CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H is internally consistent with a local privilege escalation that needs only low privileges and no user interaction, matching the assessment that a malicious or compromised app already running at User level is the prerequisite.
Know when the next one hits your stack
- 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:L/UI:N/S:U/C:H/I:H/A:H
Local app-level foothold gives AV:L/PR:L; permission bypass needs no interaction (UI:N/AC:L) and yields full privilege escalation, so C:H/I:H/A:H.
Primary rating from Vendor (Google_Devices).
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
3DescriptionCVE.org
In multiple locations, there is a possible permission bypass due to a logic error in the code. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.
Executive ViewAI
CVE-2026-55359 affects Google Android and Pixel devices, where a malicious or compromised app already running at User level could bypass permission checks and gain elevated privileges, creating a mobile endpoint data-integrity and confidentiality risk. Organizations with large Android/Pixel fleets should care because untrusted or sideloaded apps could turn a single compromised device into a broader mobile security exposure, though no public exploit identified at time of analysis and EPSS is low. No vendor-released patch identified at time of analysis, making interim mobile hardening and patch tracking the immediate leadership priority.
No vendor-released patch identified at time of analysis; use Managed Google Play/application allowlisting, disable sideloading and unknown sources, restrict developer options, enforce least privilege on apps, deploy mobile threat defense, and monitor for anomalous privilege escalation.
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.
EUVD-2026-78952
GHSA-pvg8-xvmx-xhrq
NVD
CVE.org
EPSS
VulDB
Exploit-DB