EUVD-2026-79002
GHSA-m5hw-4w2f-h6fq
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall/run unprivileged app on device
-
DeliverySubmit crafted VP9 stream to hardware decoder
-
ExploitTrigger OOB read via faulty bounds check in Vp9DecEndOfStream
-
ExecutionLeak adjacent process memory
-
ImpactUse disclosed data for local privilege escalation
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the attacker to already execute local code on the affected Pixel/Android device (AV:L) - typically an installed app - that can hand a crafted VP9 bitstream to the platform's hardware VP9 decoder path (vp9hwd_output.cc Vp9DecEndOfStream). No user interaction (UI:N) and no pre-existing elevated privileges (PR:N) are needed, but exploitation is confined to devices using this Google/Tensor hardware VP9 decode implementation and is gated by whether an attacker can reach the codec with attacker-controlled input. It is not remotely exploitable without a local foothold. |
| Impact | Signals point to a low real-world priority despite the 8.4 (High) vendor CVSS. The vector is explicitly local (AV:L) - exploitation requires already running unprivileged code on the Android/Pixel device, so this is not remotely reachable. EPSS is very low at 0.11% (2nd percentile), there is no CISA KEV listing (no public exploit identified at time of analysis), and no POC is referenced; SSVC/automatable data is not provided. Note a signal conflict: the description states an out-of-bounds READ from an incorrect bounds check (CWE-125), a primitive that primarily yields information disclosure, yet the vendor scores full C:H/I:H/A:H and labels it 'escalation of privilege' - this is standard Android bulletin boilerplate and likely overstates the integrity/availability impact. Treat the I:H/A:H as generous. Realistic priority: routine patch-cycle item, not an emergency; the low-and-local profile means targeted local abuse (e.g., as one link in a chain) rather than widespread exploitation. |
| Exploit ScenarioDerived | A malicious or compromised app installed on a Pixel device feeds a crafted VP9 video stream to the hardware decoder; the incorrect bounds check in Vp9DecEndOfStream triggers an out-of-bounds read within the media codec process, no user interaction required. The leaked memory contents can disclose sensitive data from adjacent buffers, potentially aiding a broader privilege-escalation chain. No public exploit code has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 16, 2026
An out-of-bounds read in the Android hardware VP9 decode path (Vp9DecEndOfStream in vp9hwd_output.cc) permits a locally installed app that can feed a crafted VP9 bitstream to the platform decoder to read memory beyond the intended buffer, leaking process data. Exploitation requires a local foothold (AV:L) - an app already running on the device - but no additional privileges (PR:N) and no user interaction (UI:N); the flaw is confined to devices using Google/Tensor's hardware VP9 decode implementation and is not remotely exploitable. Independent reassessment of the impact narrows this to information disclosure (C:H/I:N/A:L) rather than the vendor's code-execution framing, and no public exploit code or confirmed active exploitation was identified at time of analysis; EPSS is 0.11% (2nd percentile), indicating very low predicted real-world exploitation activity.
Earlier versions of this analysis (1)
Out-of-bounds read in the Android VP9 hardware decoder's end-of-stream handling (Vp9DecEndOfStream in vp9hwd_output.cc) lets a local attacker who already runs code on the device - typically a malicious or compromised app holding normal app privileges - drive the decoder with a crafted VP9 stream and escalate privileges, achieving high impact to confidentiality, integrity, and availability. Exploitation is strictly local: it requires the attacker to first obtain on-device code execution that can submit a malicious VP9 bitstream to the affected hardware-decoder path on an unpatched Android/Pixel build, and once that condition is met no user interaction is needed and there is no remote or network vector. No public exploit code and no confirmed active exploitation were identified at time of analysis; the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this 7.8 HIGH, consistent with the independent assessment.
RemediationAI
The primary action is to apply Google's September 2026 Pixel/Android security bulletin update (https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01), which is where the fix for CVE-2026-58699 is published; the supplied data does not include an exact patch build or version string, so reference the bulletin's build list for the confirmed patched level (patch status: "Patch available per vendor advisory"). Because exploitation is purely local and requires an attacker-controlled VP9 stream to reach the hardware decoder, the most effective compensating controls before patching are on the ingress side: keep Google Play Protect and any mobile threat defense / app-vetting in place and restrict sideloading and untrusted APK installation (trade-off: blocks legitimate internal app deployment, so allowlist approved packages), and avoid opening or automatically previewing untrusted VP9/WebM video content from unvetted sources in apps that hand streams straight to the platform codec (trade-off: degrades user experience and is only a partial control, since any installed app can synthesize a bitstream). Disabling the hardware VP9 decoder in favor of a software fallback is not a supported end-user toggle on Android and would carry severe battery and performance costs if attempted through system policy; relying on Android's media codec process sandboxing limits lateral impact but does not fix the read itself. There is no indication of active exploitation (not in CISA KEV) and no publicly available exploit code, so this should be scheduled at normal patch cadence rather than treated as an emergency - but because the bug class is an information-disclosure read, any post-patch forensics should look for anomalous VP9 decode crashes or unusual process-memory disclosure from media apps on unpatched devices.
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 code lives in vp9hwd_output.cc, the output/end-of-frame handling layer of a hardware-accelerated VP9 video decoder - the same VP9 hardware decode path used by Google platforms (tagged Google/Android, reported by Google_Devices) and exposed to apps through Android's media codec framework. VP9 is a royalty-free video codec whose bitstreams carry frame headers, tile data and reference-frame metadata; the decoder must validate derived sizes and indices against the allocated output buffers before reading them. CWE-125 (Out-of-bounds read) here arises because the bounds check performed in Vp9DecEndOfStream is incorrect - an end-of-stream / end-of-frame condition is validated against the wrong limit or in the wrong order - so a manipulated bitstream can drive an index or length past the buffer boundary and cause the decoder to read adjacent memory. The vendor CPE (cpe:2.3:a:google:android:*:*:*:*:*:*:*) and ENISA EUVD entry (EUVD-2026-79002, listing "Android Android kernel") place this in the Android platform codec stack rather than in an app or library that a user can simply upgrade. Because the primitive is a read, the credible consequence is disclosure of in-process decoder memory (potentially including other media buffers or heap metadata) rather than direct control-flow hijack; that is why the independent assessment scores C:H with I:N and A:L. The practical reachability gate is whether attacker-controlled VP9 data can actually be delivered to this hardware decoder from within the app sandbox or media codec process.
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 unprivileged app reaches the codec (AV:L/PR:N/UI:N); an OOB read yields memory disclosure (C:H) and at most a crash (A:L), with no integrity impact (I:N).
Primary rating from Vendor (Google_Devices).
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
5DescriptionCVE.org
In Vp9DecEndOfStream of vp9hwd_output.cc, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Articles & Coverage 1
Executive ViewAI
A memory-disclosure flaw in Google/Tensor's hardware VP9 video decoder on Android (CVE-2026-58699, CVSS 8.4) lets a locally installed app read data beyond its intended buffer while decoding a crafted video stream. Only mobile devices built on that specific decoder implementation are exposed, and the attacker must already have an app running on the device, so the practical risk is leakage of media-process data rather than remote compromise. Leadership should care because no vendor patch is currently available, making exposure management dependent on app-governance controls and vendor timelines rather than a deployable fix.
No vendor-released patch identified at time of analysis. Interim options: restrict installs to vetted, allowlisted applications and enforce Play Protect with unknown-source and sideloading blocked via EMM/MDM; limit the number of apps permitted to process untrusted video content on affected Google/Tensor devices; use software VP9 decoding where a vendor-supported configuration exists; monitor for anomalous memory access or unexpected data exfiltration from media applications; and note that the CVSS vector indicates a local (AV:L) attack requiring no additional privileges (PR:N) or user interaction (UI:N), while no public exploit was identified at time of analysis.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
Exploit-DB