Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted Vorbis audio to device
-
ExploitCodec parses malformed codebook
-
ExecutionLogic error causes out-of-bounds read in decode_packed_entry_number
-
ImpactAdjacent process memory disclosed to attacker
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 | Exploitation requires the affected device to decode an attacker-crafted Vorbis audio stream whose codebook data triggers the logic error in decode_packed_entry_number (codebook.c); the vulnerable path is the Vorbis/Tremor codebook decoder reachable when the system processes such audio. Per the vendor CVSS vector the attack is network-reachable, unauthenticated (PR:N), and needs no user interaction (UI:N). Limiting factors that reduce real-world severity: impact is restricted to low-confidentiality information disclosure (C:L) with no integrity or availability effect and no code execution, so the attacker gains leaked memory contents rather than control; affected scope is Android 14 through 17. The precise content-delivery path that causes the device to decode the malicious stream is not described in the available sources. |
| Impact | Signals are consistent and point to a genuine-but-moderate issue rather than an urgent emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3 Medium) describes a remotely reachable, low-complexity, unauthenticated flaw with no user interaction, but the impact is confined to low-confidentiality information disclosure (C:L) with no integrity or availability effect - consistent with an out-of-bounds read (CWE-125) that leaks adjacent memory rather than enabling code execution. EPSS is low at 0.17% (6th percentile), the CVE is NOT on CISA KEV, and no public exploit or PoC reference is present in the supplied data, so there is no evidence of active or imminent widespread exploitation. The vuln.today decision label is 'this_month', which aligns with a routine-but-timely patch priority rather than act_now/emergency. The one tension worth flagging: the CVSS vector asserts AV:N and UI:N, yet the flaw lives in a media/audio codec path (Vorbis codebook decoding), where triggering normally depends on the device processing attacker-supplied audio content; the supplied evidence does not describe the exact delivery path, so treat the 'no interaction, network' framing as the vendor's rating rather than an independently confirmed drive-by. Net: a real vulnerability warranting inclusion in the normal monthly Android patch cycle, not a drop-everything priority. |
| Exploit ScenarioDerived | An attacker crafts a malformed Vorbis audio stream whose codebook triggers the logic error in decode_packed_entry_number, then gets an Android device to decode it (for example via content delivered over the network). When the codec parses the crafted codebook, the out-of-bounds read exposes adjacent process memory, disclosing information to the attacker with no user interaction and no elevated privileges. No public exploit identified at time of analysis; AC:L indicates a crafted input reliably triggers the condition, though the exact trigger details are not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
An out-of-bounds read in Android's Vorbis codebook decoder (decode_packed_entry_number in codebook.c) lets remote, unauthenticated attackers leak limited memory contents by having the device process a crafted audio stream, with no user interaction required per the vendor CVSS vector. Impact is confined to low-confidentiality information disclosure on Android 14 through 17, with no integrity or availability effect and no code execution. No public exploit has been identified at time of analysis; EPSS is low at 0.17% (6th percentile) and there is no CISA KEV listing, so this is a moderate, patch-cycle issue rather than an emergency.
RemediationAI
No vendor-released patch version is identified in the provided data, so remediation must be driven by the Android Security Bulletin 2026-11-01 at https://source.android.com/docs/security/bulletin/2026/2026-11-01, which lists the patched build levels for Android 14, 15, 16, 16-qpr2, and 17; administrators and users should confirm their device build against that bulletin and apply the corresponding Android security update. The available sources do not describe a specific configuration workaround or feature that can be disabled to avoid the vulnerable Vorbis codebook decode path, so updating to a build level covered by the bulletin is the only remediation the evidence supports.
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 flaw is a CWE-125 out-of-bounds read caused by a logic error inside decode_packed_entry_number in codebook.c, part of the Vorbis/Tremor codebook decoding path used when Android processes Vorbis audio. Because the decoder consumes attacker-supplied codebook data, a malformed stream can drive the routine past the bounds of an in-memory structure and expose adjacent memory back through the decode result. Per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N vector the issue is network-reachable and unauthenticated with no user interaction, but the impact is capped at low confidentiality loss with unchanged scope, so the attacker obtains leaked memory contents rather than code execution or persistence. The precise content-delivery path that causes an affected device to decode the malicious stream, and the exact malformed codebook structure that trips the logic error, are not described in the available sources.
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:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Remotely reachable codec flaw needing no auth or interaction (AV:N/PR:N/UI:N); an out-of-bounds read leaks memory, so C:L with I:N/A:N.
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In decode_packed_entry_number of codebook.c, there is a possible out-of-bounds read due to a logic error in the code. This could lead to remote information disclosure with no additional 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
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
EUVD-2026-115429
GHSA-6c4g-7jcf-ph8m
NVD
CVE.org
EPSS
Exploit-DB