Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local code execution on Pixel device
-
DeliveryAccess EdgeTPU ExecuteGraph command handler
-
ExploitSubmit crafted graph triggering integer overflow
-
ExecutionOut-of-bounds write corrupts firmware memory
-
ImpactEscalate to privileged execution
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation 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 to the device and the ability to invoke the EdgeTPU firmware's ExecuteGraph command handler - i.e., a process that can reach the EdgeTPU device interface on an affected Google Pixel/Tensor device. No user interaction is required (UI:N). The condition that limits exploitation is attacker-privilege level, which is unresolved in the sources: the CVSS vector asserts PR:L (low-privileged local caller), while the description states 'root privileges needed,' which would make this a low-value primitive requiring pre-existing root. Further limiting factors: the vector is local only (not remotely reachable), it is non-automatable per SSVC, and it affects only devices carrying EdgeTPU firmware (Pixel/Tensor), not the broader Android ecosystem. The precise integer-overflow trigger within ExecuteGraph beyond 'crafted input causing an out-of-bounds write' is not described in the available sources. |
| Impact | This is a locally-exploitable memory-corruption flaw (CWE-787 out-of-bounds write via integer overflow) in the EdgeTPU firmware's ExecuteGraph command handler on Google Pixel/Tensor devices. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and SSVC 'Technical Impact: total' agree that successful exploitation yields complete compromise of the targeted component, but every exposure signal points away from widespread, urgent risk: SSVC Exploitation is 'none', SSVC Automatable is 'no' (consistent with a local-only vector that cannot be sprayed remotely), EPSS is 0.07% (0th percentile), and the vulnerability is NOT in CISA KEV. The vuln.today priority is 'this_week' - meaning patch within the normal cycle, not an emergency. CONFLICTING DATA: the description states 'local escalation of privilege with root privileges needed,' which reads as requiring root already (PR:H) - directly at odds with the official CVSS PR:L and with the premise of a privilege-escalation bug; this ambiguity should be resolved against the Android/Pixel bulletin before assigning an attacker-privilege assumption. Net: a genuinely severe local EoP primitive but a low-probability, non-automatable, hardware-specific issue - a real but non-urgent priority, not a high-CVSS-but-low-impact case nor an actively-exploited emergency. |
| Exploit ScenarioDerived | A malicious or compromised app/process already running on a Pixel device with access to the EdgeTPU device interface submits a crafted graph to the ExecuteGraph command handler, triggering an integer overflow that produces an out-of-bounds write in EdgeTPU firmware. The attacker leverages the memory corruption to escalate privileges locally without any user interaction. No public exploit or proof-of-concept is identified in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Local memory corruption in Google Pixel/Tensor EdgeTPU firmware can be triggered through the ExecuteGraph command handler, where an integer overflow can cause an out-of-bounds write (CWE-787). A local caller able to reach the EdgeTPU device interface may be able to turn this into privilege escalation, but the sources conflict on prerequisites: the CVSS vector asserts PR:L while the description says root privileges are needed. No public exploit has been identified at time of analysis, SSVC reports no exploitation and non-automatable conditions, and EPSS is 0.07% (0th percentile).
RemediationAI
Apply the Pixel security update referenced in Google's June 2026 bulletin at https://source.android.com/docs/security/bulletin/pixel/2026/2026-06-01; the supplied data does not state an exact fixed build, so verify the bulletin for the applicable Pixel/Tensor firmware version. If the update cannot be applied promptly, restrict which local processes can reach the EdgeTPU device interface to trusted privileged components, accepting that this reduces exposure without fixing the firmware and may break on-device ML features. Because the CVSS vector asserts PR:L while the description says root privileges are needed, do not treat the root prerequisite as a reliable mitigation until the vendor clarifies; prioritize as this_week.
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
EdgeTPU is Google's edge AI accelerator used in Pixel/Tensor devices, and ExecuteGraph is the firmware command handler that processes graph-execution requests. The flaw is an integer overflow that leads to an out-of-bounds write in firmware memory (CWE-787); the exact arithmetic error and crafted-input structure are not described in the available sources. The CPE maps to google:android with a wildcard version, but the affected code is EdgeTPU firmware, so exposure is limited to devices carrying that firmware rather than the broader Android ecosystem. Exploitation requires local access to the device and the ability to invoke the ExecuteGraph handler through the EdgeTPU device interface; the CVSS vector records AV:L/AC:L/PR:L/UI:N, while the description states root privileges are needed, leaving the required attacker privilege level unresolved.
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:L/UI:N/S:U/C:H/I:H/A:H
Local access to the EdgeTPU device interface (AV:L) from a low-privileged caller per the official vector (PR:L, though the description's 'root needed' conflicts); no user interaction, and total component compromise gives C/I/A:H.
Primary rating from Vendor (Google_Devices).
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
3DescriptionCVE.org
In ExecuteGraph command handler of EdgeTPU firmware, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with root privileges needed. User interaction is not needed for exploitation.
Executive ViewAI
CVE-2026-0150 is a high-severity memory corruption vulnerability in Google Pixel EdgeTPU firmware that, while requiring local access and conflicting prerequisites, could enable privilege escalation on affected devices. Leadership should care because this affects Pixel devices potentially used by employees, and with no patch available, risk mitigation relies on restricting local interface access.
Restrict local access to EdgeTPU device interface to trusted users; disable developer options and USB debugging on managed devices; enforce device encryption and strong authentication; monitor for vendor patch and apply when available.
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
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-37184
GHSA-73jc-hjc2-926j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB