Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain System-level code execution
-
DeliverySend malformed input to VPU interface
-
ExploitTrigger shared-memory overwrite (improper input validation)
-
ExecutionCorrupt privileged execution context
-
ImpactEscalate privileges beyond System
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the attacker to already possess System execution privileges on the affected Android/Pixel device and to be able to reach the VPU (Video Processing Unit) component with attacker-controlled input; the flaw is an improper-input-validation shared-memory overwrite in that component. No user interaction is required (UI:N). The primary limiting factors are the high pre-existing privilege requirement (PR:H - this is not reachable by an ordinary unprivileged app) and local-only access (AV:L, no remote or network vector); it also depends on running an unpatched build predating the 2026-09-01 Pixel/Android security patch level. |
| Impact | This is a genuine but constrained local privilege-escalation issue, not a top-tier priority. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U) and the description both agree on a locally-exploitable flaw that requires the attacker to ALREADY hold System execution privileges before triggering the shared-memory overwrite in the VPU (Video Processing Unit) component - so this is a System-to-higher (kernel/hardware-context) escalation, not a path from an unprivileged app. That high pre-requisite (PR:H) is the single biggest mitigating factor and is fully consistent between the vector and the description, so there is no AV/PR conflict to resolve here. Exploitation signals are uniformly cold: EPSS is 0.11% (2nd percentile), there is no CISA KEV listing, and no public exploit code was identified. The vendor-assigned C:H/I:H/A:H triad is somewhat generous given the attacker is already at System - realistic gain is corruption of a more-privileged execution context rather than a fresh disclosure of previously-inaccessible secrets. Net: a legitimate patch-worthy Android/Pixel component bug, but real-world urgency is low absent any exploitation evidence and given the System-privilege gate. |
| Exploit ScenarioDerived | An attacker who has already achieved code execution at Android's System privilege level (e.g., via a compromised system service or a prior chained bug) sends crafted input to the VPU that fails input validation, causing a controlled overwrite of shared memory. This corruption is leveraged to escalate beyond System into a more privileged execution context, with no user interaction required. No public proof-of-concept exploit is known at the time of analysis. |
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's Video Processing Unit (VPU) component lets an attacker who already holds System-level execution privileges supply improperly validated input that overwrites shared memory, yielding high confidentiality, integrity, and availability impact with no user interaction required. The flaw (CWE-20) affects Android/Pixel builds that predate the 2026-09-01 security patch level and is only reachable locally, not over a network. Exploitation is constrained by the PR:H prerequisite - an ordinary unprivileged app cannot reach the vulnerable path - and no public exploit code or confirmed active exploitation has been identified at time of analysis; EPSS is correspondingly low at 0.11% (2nd percentile).
RemediationAI
The primary fix is to apply the vendor patch identified in the Android/Pixel security bulletin for 2026-09-01 at https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01, which raises the device security patch level to or above 2026-09-01; this is the only vendor-released remediation referenced in the available data, and no separate fix version string beyond that bulletin is provided, so patched builds should be confirmed against the bulletin rather than an invented version number. Until devices can be updated, compensating controls must be chosen with the understanding that the flaw requires an attacker to already hold System execution privileges and to reach the VPU locally, so there is no network-facing mitigation to apply and no configuration toggle that removes the vulnerable code path. Effective interim measures are therefore hardening and detection oriented: treat any context that grants System execution privileges as trusted-only, restrict installation and elevation grants so unprivileged or untrusted apps cannot obtain that level, and monitor for anomalous VPU activity or unexpected shared-memory manipulation on unpatched devices; the trade-off is that these reduce the attack surface and likelihood of reaching the prerequisite privilege level but do not eliminate the underlying improper-input-validation defect, so they are strictly temporary until the 2026-09-01 patch is applied. Because no public exploit code has been identified, there is no exploit-specific blocklist or signature to deploy at this time.
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 affected technology is the Video Processing Unit (VPU) within Google's Android platform, tracked by CPE cpe:2.3:a:google:android with a wildcard version range, and listed by ENISA EUVD as affecting the Android kernel component. The root cause is CWE-20 (Improper Input Validation): input reaching the VPU is not adequately validated before being used in a shared-memory operation, allowing the contents of shared memory to be overwritten. Because the vulnerability class is a memory-corruption condition in a privileged component, the CVSS vector CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H characterizes it as locally exploitable (AV:L), low attack complexity (AC:L), requiring high pre-existing privileges (PR:H) with no user interaction (UI:N), scoped to the same security authority (S:U), and producing high confidentiality, integrity, and availability impact. The PR:H metric is the decisive constraint: this is not reachable by an ordinary sandboxed application, but only from a context that already has System execution privileges, so the practical gain is privilege escalation or persistence beyond that existing level rather than initial compromise. Exploitation also depends on the device running an unpatched Android/Pixel build below the 2026-09-01 patch level.
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:H/UI:N/S:U/C:H/I:H/A:H
Local vector and low complexity per description; PR:H because System execution privileges are explicitly required first; UI:N stated; C/I/A:H retained for memory-corruption EoP though generous given the attacker is already System.
Primary rating from Vendor (Google_Devices).
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
3DescriptionCVE.org
In VPU, there is a possible shared memory overwrite due to improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
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-78961
GHSA-3p2v-g86r-3rwm
NVD
CVE.org
EPSS
VulDB
Exploit-DB