CVE-2026-0150
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA vulnerability exists in the ExecuteGraph command handler of EdgeTPU firmware where an integer overflow can cause an out-of-bounds write. This allows a local attacker to escalate privileges to root without any user interaction. The attack requires local access but no elevated privileges to trigger the overflow.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify EdgeTPU hardware presenceCheck system hardware information for Google EdgeTPU or Tensor Processing Unit components. On Android, this may appear in /proc/cpuinfo, lspci, or device-specific hardware registers. Look for 'EdgeTPU', 'Coral', 'TPU', or Google-specific tensor processing identifiers.Affected if EdgeTPU hardware is present on the device
-
Verify ExecuteGraph command handler availabilityDetermine if the ExecuteGraph command handler interface is exposed. This is typically accessed through EdgeTPU runtime libraries (libedgetpu.so) or the EdgeTPU driver API. Check if the EdgeTPU service or daemon is running and accepting graph execution requests.Affected if EdgeTPU runtime is active and ExecuteGraph handler is accessible to local users
-
Confirm local access to EdgeTPU interfaceReview file permissions and access controls on EdgeTPU device nodes (typically /dev/edge*tpu* or /dev/coral*). Check if any local unprivileged user can interact with the EdgeTPU interface.Affected if Non-privileged local users have direct access to EdgeTPU device nodes without restriction
-
Assess physical access exposureEvaluate whether the device with EdgeTPU is in a physically accessible location. Determine if local attackers could gain shell access or execute code on the affected system.Affected if Physical or local shell access to the system is possible by untrusted individuals
-
Check Android system scopeConfirm the Android version and whether EdgeTPU features are enabled. Some Android devices with hardware ML accelerators may expose EdgeTPU functionality through the Android Neural Networks API (NNAPI) or TensorFlow Lite delegate.Affected if Running any version of Android with EdgeTPU hardware and ML acceleration features enabled
A system is affected if it contains Google EdgeTPU hardware and the ExecuteGraph command handler is accessible to a local unprivileged user, regardless of Android version since all versions are impacted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied firmware update for EdgeTPU devices once available. Until then, restrict physical and local access to systems containing EdgeTPU hardware to limit exposure.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0150 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data