Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconDeploy rogue cellular base station
-
DeliveryLure or force nearby UE to camp on attacker cell
-
ExploitSend malformed modem protocol message
-
InstallTrigger missing bounds check
-
C2Out-of-bounds write corrupts modem memory
-
ExecuteModem stack crashes
-
ImpactUE loses all cellular connectivity
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 the target User Equipment (UE) - any mobile device containing one of the 33 listed MediaTek chipsets - to be physically connected (camped) to a rogue cellular base station under attacker control. The attacker must operate or control radio infrastructure capable of impersonating a legitimate cell tower with sufficient signal strength to cause the target device to preferentially attach to it. This is not a conventional internet-reachable attack; it requires radio-frequency proximity and cellular infrastructure expertise. No authentication is required at the modem protocol layer (PR:N per CVSS vector), and no user interaction or application-layer action by the victim is needed once the device attaches to the rogue cell. Exploitation is limited to the modem subsystem's availability - confidentiality and integrity of device data are not impacted. The non-default nature of the attack environment (rogue base station setup) materially limits opportunistic or automated exploitation despite PR:N and UI:N ratings. |
| Impact | The CVSS 3.1 score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) accurately captures both the severity and the constraint: the High Attack Complexity reflects the real-world barrier of deploying or compromising a cellular base station, which requires significant resources and technical capability beyond a typical threat actor. Impact is limited strictly to availability (A:H) - a modem crash causes loss of cellular connectivity but there is no confirmed confidentiality or integrity impact. No CISA KEV listing exists, no public exploit or POC has been identified, and no EPSS data was provided, all of which are consistent with the AC:H constraint reducing opportunistic exploitation. The risk is most credible in targeted scenarios - nation-state actors, organized crime with radio infrastructure access, or IMSI-catcher operators. The absence of a scope change (S:U) confirms the impact is contained to the UE modem stack. Despite the moderate aggregate CVSS score, fleet-level risk is elevated because the 33 affected chipsets represent a very large share of mid-range to flagship Android devices globally; a single rogue base station could affect every reachable device simultaneously. |
| Exploit ScenarioDerived | An attacker with access to software-defined radio (SDR) equipment and cellular infrastructure knowledge deploys a rogue LTE or 5G base station - a capability within reach of nation-state actors and some organized criminal groups - and broadcasts signals strong enough to force nearby devices to camp on the attacker-controlled cell. Once a target UE attaches to the rogue base station, the attacker transmits a crafted modem protocol message containing malformed data that triggers the missing bounds check, causing an out-of-bounds write in modem memory, crashing the modem stack and rendering the device unable to make or receive cellular calls or data until rebooted. No public exploit code has been identified, meaning exploitation currently requires independent vulnerability research and baseband development expertise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Out-of-bounds write in MediaTek modem firmware allows a network-adjacent attacker controlling a rogue cellular base station to remotely crash affected User Equipment (UE), resulting in denial of service. Thirty-three distinct MediaTek chipsets - spanning flagship mobile SoCs (MT6991, MT6989, MT6985) to tablet and IoT chipsets (MT8795T, MT8893) - contain the vulnerable modem component identified under Patch IDs MOLY01267281 and MOLY01318201. No public exploit code has been identified at time of analysis, and the attack is non-trivial due to the requirement for attacker-controlled cellular infrastructure, but the sheer deployment scale of affected chipsets across Android devices makes the aggregate exposure significant.
RemediationAI
MediaTek has released patches under Patch IDs MOLY01267281 and MOLY01318201 (Issue ID: MSV-6486), distributed to OEM partners via the July 2026 Product Security Bulletin at https://corp.mediatek.com/product-security-bulletin/July-2026. End users should apply Android security updates from their device manufacturer as soon as patches incorporating these modem fixes become available; the exact OEM firmware version will vary by device. No specific patched modem firmware version is publicly enumerated in available data - affected version remediation is confirmed by vendor advisory only. As a compensating control where patching is delayed, disabling cellular data and relying on Wi-Fi calling reduces the attack surface by limiting modem exposure to cellular base station signaling, though voice calls over the native cellular stack may still be affected. Enabling VoLTE airplane-mode fallback and restricting devices to known network operators via carrier lock settings can reduce exposure to rogue base stations in high-risk environments, at the cost of reduced cellular availability.
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 vulnerability resides in the MediaTek modem baseband firmware (CWE-787: Out-of-bounds Write), which handles the cellular protocol stack for 4G/5G radio communications on affected SoCs. A missing bounds check in the modem's signal or message processing path allows a crafted wireless transmission from a rogue base station to write data beyond the intended buffer boundary in modem memory. Affected chipsets are identified by CPE cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:* and include high-volume Dimensity-series mobile SoCs (MT6985, MT6989, MT6991, MT6993) and Kompanio/Helio tablet chipsets (MT8795T, MT8893, MT8883). The flaw is in the modem subsystem rather than the application processor, meaning it operates largely independently of the host OS and is not gated by Android security layers.
Know when Mediatek Chipset 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:H/PR:N/UI:N/S:U/C:N/I:N/A:H
AV:N reflects cellular network delivery; AC:H captures the rogue base station prerequisite; PR:N and UI:N are accurate as the modem processes signals autonomously; A:H for modem crash; C:N and I:N as no data exfiltration or integrity impact is described.
Primary rating from Vendor (MediaTek).
CVSS VectorVendor: MediaTek
Lifecycle Timeline
3DescriptionCVE.org
In Modem, there is a possible out of bounds write due to a missing bounds check. This could lead to remote denial of service, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01267281 / MOLY01318201; Issue ID: MSV-6486.
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.
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Related Vulnerabilities in MediaTek Modem Remote DoS and Privilege Escalation
View all 6More in Mediatek Chipset
View allOut-of-bounds write in MediaTek modem firmware enables remote privilege escalation when devices connect to attacker-cont
Heap buffer overflow in the vdec (video decoder) kernel driver across 53+ MediaTek SoCs allows a local unprivileged atta
Local privilege escalation in MediaTek's vdec (video decoder) kernel driver affects more than 53 distinct chipset varian
Heap-based buffer overflow in the MediaTek WLAN AP driver enables an adjacent-network attacker to escalate privileges wi
Out-of-bounds write in MediaTek modem chipset implementations allows remote privilege escalation when user equipment con
Heap buffer overflow in the MediaTek WLAN access point driver allows adjacent-network attackers with low-privilege user
Local privilege escalation in MediaTek's Bluetooth driver affects six Wi-Fi/Bluetooth combo chipsets (MT7902, MT7920, MT
Local privilege escalation in MediaTek GenieZone (trusted execution environment) allows an attacker who has already gain
Privilege escalation in MediaTek's Android Telephony component enables any locally-installed application - regardless of
Out-of-bounds read in MediaTek modem firmware across 19 chipsets enables remote denial of service when a User Equipment
Privilege escalation via a double-free memory corruption bug in camera middleware affects 17 MediaTek chipset variants,
EUVD-2026-40874
GHSA-69rh-fj32-xxwg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB