Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconPosition rogue base station in radio range
-
DeliverySend crafted cellular signaling to modem
-
ExploitTrigger heap buffer overflow in parser
-
InstallOut-of-bounds heap write
-
C2Corrupt modem heap structures
-
ExecuteExecute code in baseband context
-
ImpactCompromise device radio stack
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution 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 attacker to be within adjacent/proximal cellular radio range of the target and able to inject crafted over-the-air signaling that reaches the vulnerable Cellular Modem parsing path - typically via a rogue base station, IMSI catcher-class equipment, or a compromised small cell, which is why the vector is AV:A rather than AV:N. It requires no user interaction (UI:N), and the CVSS vector marks low privileges (PR:L), which conflicts with the description's statement that no additional execution privileges are needed - this discrepancy should be resolved against the vendor bulletin before assuming unauthenticated reachability. Limiting factors: the flaw is not exploitable over the internet (proximity to the radio interface is mandatory), it is platform/OEM-specific to devices carrying the affected modem implementation, and exploitation is harder if the device is on Wi-Fi-only with the cellular radio disabled or if legacy 2G/3G fallback is turned off. No preconditions involving a specific app, endpoint, or non-default configuration setting were identified in the available data. |
| Impact | The CVSS 3.1 vector scores this 8.0 with AV:A (adjacent network), AC:L, PR:L, UI:N and high C/I/A, which places exploitation squarely in the radio-proximity domain rather than the internet-remote domain: an attacker needs to be within cellular/adjacent range (for example operating a rogue base station or compromised small cell) rather than merely having an IP path to the device. EPSS and CISA KEV data were not supplied, and no public exploit code was indicated, so this is not confirmed as actively exploited; treat it as a high-severity, plausibly automatable radio-adjacent bug whose real priority depends on whether the modem parsing path is reachable pre-authentication. There is an internal inconsistency worth flagging: the description states no additional execution privileges are needed, while the CVSS vector marks PR:L - the effective privilege precondition should be verified against the vendor bulletin before teams downgrade or upgrade severity. Because adjacent-network exploitation is automatable and requires no user interaction, this is more actionable than a typical local-only memory-safety bug, but less urgent than an internet-facing unauthenticated RCE. |
| Exploit ScenarioDerived | An attacker deploys a rogue base station or compromised small cell within radio range of the target device and transmits crafted cellular signaling messages that reach the vulnerable modem parsing routine. The malformed input overflows a heap buffer, producing an out-of-bounds write that corrupts modem heap metadata or a function pointer and allows code execution in the baseband context without any user interaction. Because the attack is proximity-based and automated, it can be run against many devices passing through a physical area, and no public exploit code has been identified to date, meaning a working attack would currently require custom tooling or a software-defined-radio setup. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 15, 2026
A heap-based buffer overflow (out-of-bounds write) exists in the Android Cellular Modem component, allowing an attacker within adjacent/proximal radio range to corrupt heap memory and potentially execute code in the modem context without user interaction. The flaw carries a CVSS base score of 8.0 (AV:A/AC:L/PR:L/UI:N) and affects Google Android devices per the Android/Google Devices CPE. No public exploit code or CISA KEV listing was provided at time of analysis, so exploitation status is unconfirmed; the vendor fix is documented in the September 2026 Pixel/Android Security Bulletin.
RemediationAI
Apply the vendor fix delivered in the September 2026 Android/Pixel Security Bulletin (https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01) by installing the OTA update with the corresponding security patch level; because this is modem/baseband code, the fix must come through a full system OTA rather than a Google Play system update, so verify the build number rather than assuming monthly Play updates covered it. Where immediate patching is not possible, the effective compensating control is to reduce radio exposure: disable cellular data and, where the device allows it, disable the cellular radio entirely and operate over Wi-Fi only (trade-off: loss of voice/SMS and mobile connectivity), or disable legacy 2G/3G fallback in favor of LTE/5G-only to shrink exposure to downgrade-style rogue base station attacks (trade-off: reduced coverage in areas without modern RAN). Organizations with high-value targets, such as executives or field devices, should consider RF-shielded storage or pouches when in untrusted physical locations (trade-off: operational inconvenience and no connectivity while shielded). No vendor-released standalone modem patch outside the full OTA was identified at time of analysis.
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 vulnerable component is the cellular modem (baseband) firmware shipped on Google Android devices, tracked under CPE cpe:2.3:a:google:android and listed by ENISA EUVD as affecting the Android kernel/modem stack. The root cause is CWE-122 (heap-based buffer overflow), an out-of-bounds write in which a length or index derived from attacker-influenced cellular protocol data exceeds the bounds of a heap allocation, corrupting adjacent memory. Baseband/telephony stacks parse a large, complex attack surface of radio-layer messages (network signaling, SMS/PDU, connection-establishment parameters) before the application processor is involved, so memory-safety defects here can be reachable purely from the radio interface. Heap corruption in this context can be steered toward control-flow hijack inside the modem's execution environment, which typically has direct access to shared memory and device-wide communication paths.
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:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack is over the cellular radio interface (AV:A), requires low-level preconditions per the stated PR:L, needs no user interaction, and yields full modem memory compromise.
Primary rating from Vendor (Google_Devices).
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
2DescriptionCVE.org
In Cellular Modem, there is a possible out-of-bounds write due to a heap buffer overflow. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
Articles & Coverage 1
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.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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-78975
GHSA-9vxv-54xv-q68g
NVD
CVE.org
EPSS
VulDB
Exploit-DB