Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain initial device foothold
-
DeliveryEscalate to System privilege via separate exploit
-
ExploitCraft malicious Telephony subsystem input
-
InstallTrigger heap buffer overflow
-
C2Corrupt adjacent heap memory structures
-
ExecuteRedirect execution flow to attacker-controlled code
-
ImpactAchieve privilege escalation beyond System level
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 explicitly requires that the attacker has already obtained System-level privilege on the target Android device - this is stated directly in the CVE description ('if a malicious actor has already obtained the System privilege') and is reflected in the CVSS PR:H metric. The device must be running one of the 22 affected MediaTek chipsets with the unpatched Telephony firmware. No user interaction is required once System privilege is held (UI:N). Exploitation is strictly local (AV:L): there is no network-facing attack surface - remote exploitation is not possible without a separate, preceding chain of access and privilege escalation exploits. The primary factor limiting exploitation is the PR:H prerequisite; an attacker operating at user-level or below cannot directly trigger this vulnerability. The unchanged scope (S:U) means the impact is confined to the compromised device and does not inherently propagate to other networked systems. |
| Impact | The CVSS 3.1 score of 6.7 (Medium) with vector AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H accurately characterises the threat: while the potential impact is severe (full C/I/A compromise), the PR:H prerequisite - requiring the attacker to already hold System-level privilege - is the dominant risk limiter. This is a privilege-chaining vulnerability, not an initial access vector. The AC:L rating indicates that once the System-privilege threshold is crossed, triggering the overflow is straightforward. EPSS data is absent from the provided intelligence, so exploitation probability cannot be quantified statistically. The vulnerability is not listed in the CISA KEV catalogue, and no public proof-of-concept has been identified, both of which support a lower near-term exploitation likelihood. Real-world risk is highest for OEM manufacturers and enterprise Android fleet operators who must integrate MediaTek-supplied patches into device firmware and push OTA updates - a process that historically introduces deployment latency. The constrained local attack surface and high privilege prerequisite make opportunistic mass exploitation implausible; targeted post-compromise use within a multi-stage chain is the credible threat model. |
| Exploit ScenarioDerived | An attacker who has already compromised an affected MediaTek-powered Android device and obtained System-level privilege - for example, through a malicious pre-installed application or a prior local privilege escalation exploit targeting a separate vulnerability - delivers specially crafted input to the Telephony subsystem, triggering the heap buffer overflow and corrupting adjacent heap structures. With AC:L once the privilege threshold is met, the attacker leverages the memory corruption to overwrite a function pointer or similar control-flow structure within the Telephony process, redirecting execution to attacker-controlled code at a higher privilege tier. No public proof-of-concept has been identified, but the low attack complexity rating suggests that a technically capable actor could develop reliable exploit code against a known-vulnerable firmware build. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Heap buffer overflow in the Telephony subsystem of MediaTek chipsets enables local privilege escalation on affected Android devices, delivering full confidentiality, integrity, and availability impact. Twenty-two specific MediaTek SoC variants are confirmed affected, spanning the MT6xxx and MT8xxx mid-range and budget families. No public exploit has been identified at time of analysis; MediaTek has issued patch ALPS11006447 via their July 2026 security bulletin, but exploitation requires a pre-existing System-level privilege on the device, making this a chaining vulnerability rather than a standalone entry vector.
RemediationAI
The primary remediation is to apply the vendor-released patch identified as ALPS11006447 (Issue ID: MSV-7871), distributed through MediaTek's July 2026 Product Security Bulletin at https://corp.mediatek.com/product-security-bulletin/July-2026. OEM device manufacturers must integrate this patch into their Android BSP and push OTA security updates to end users on affected devices; an exact patched firmware version is not independently specified in the available data beyond the patch ID. As a compensating control prior to patch deployment, defenders should enforce SELinux in enforcing mode (reducing the attack surface available to System-privilege processes), restrict sideloading and installation of applications with System-level permissions, and audit pre-installed applications for any that hold System privilege unnecessarily - since the attacker must satisfy the PR:H prerequisite before the Telephony overflow can be leveraged. These controls reduce the probability of an attacker reaching the exploit's prerequisite state but do not remediate the underlying heap overflow; patching remains mandatory.
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 component is the Android Telephony stack - the software layer managing baseband-to-application communications - as implemented on MediaTek chipsets. CWE-122 (Heap-Based Buffer Overflow) identifies the root cause: a write operation overruns the bounds of a heap-allocated buffer, corrupting adjacent memory. In telephony processing code, such corruption can overwrite heap metadata, vtable pointers, or function pointers, redirecting execution flow. The breadth of the CPE identifier (cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:*) and the EUVD listing cover 22 specific chipsets - MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6853, MT6855, MT6877, MT6883, MT6885, MT6889, MT6893, MT8695, MT8696, MT8765, MT8766, MT8766R, MT8768, MT8781, and MT8791 - indicating the vulnerable Telephony code is shared across MediaTek's mid-range and budget SoC product lines, consistent with a common firmware codebase.
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:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
System-level privilege is an explicit, confirmed prerequisite (PR:H); exploitation is local-only (AV:L); once conditions are met, AC:L and full C/I/A impact are consistent with a heap overflow yielding arbitrary code execution.
Primary rating from Vendor (MediaTek).
CVSS VectorVendor: MediaTek
Lifecycle Timeline
2DescriptionCVE.org
In Telephony, there is a possible memory corruption due to a heap buffer overflow. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS11006447; Issue ID: MSV-7871.
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
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.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
More 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
Remote privilege escalation in the baseband modem firmware of dozens of MediaTek chipsets allows an attacker operating a
Privilege escalation via a double-free memory corruption bug in camera middleware affects 17 MediaTek chipset variants,
EUVD-2026-40875
GHSA-39rh-f5c6-gchq
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB