Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious app to target device
-
DeliveryGain local execution without elevated privileges
-
ExploitInvoke exported Telephony component
-
ExecutionBypass absent permission check
-
PersistExtract sensitive subscriber or call-state data
-
ImpactExfiltrate data to attacker infrastructure
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Improper export of Android components
|
| Exploitation Conditions | Exploitation requires that an attacker have local code execution on the device, specifically a malicious or compromised application installed on the target Android device running an affected MediaTek chipset (any of the 42 SKUs listed). The CVSS vector PR:N confirms no Android permissions or elevated privileges are required - any installed app, even one with minimal declared permissions, can invoke the exported Telephony component. No non-default system configuration is required; the improper export is present in standard MediaTek Telephony builds on affected chipsets. Exploitation is bounded by: (1) physical or social-engineering access to get an app onto the device, (2) the device must use one of the 42 named MediaTek chipsets, and (3) the OEM must not have independently corrected the export in their Android build. Remote unauthenticated exploitation is not possible - local presence is mandatory. |
| Impact | The CVSS 3.1 vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N scores 6.2, which is consistent with the attack profile: local vector limits exposure relative to network-accessible flaws, but the absence of any privilege requirement (PR:N) and lack of user interaction (UI:N) means any installed application - including those with only INTERNET permission - can potentially invoke the exposed component. The C:H rating indicates meaningful telephony data is accessible, not just benign metadata. EPSS at 0.15% (5th percentile) strongly suggests no observed automated exploitation attempts, and the absence from CISA KEV corroborates this. However, this class of vulnerability is attractive to spyware and stalkerware operators who already have device-local presence through a sideloaded app. The realistic threat actor is a malicious or trojanized app rather than a remote opportunistic attacker. The sheer number of affected chipset SKUs (42 models listed) increases aggregate exposure across the Android ecosystem, particularly in markets where MediaTek dominates mid-range and budget segments. |
| Exploit ScenarioDerived | An attacker distributes a malicious Android application - potentially disguised as a utility or game - targeting devices running on an affected MediaTek chipset. Once installed, the app calls the improperly exported Telephony component without requesting sensitive permissions, silently reading subscriber identifiers (IMSI), call records, or SIM data and exfiltrating it to a remote server. No user interaction is required after installation, and the access leaves no visible indicators on the device. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Local information disclosure in the Telephony component across 42 MediaTek chipsets enables any unprivileged application on the device to extract sensitive telephony data without elevated permissions. The root cause is a missing Android permission check (CWE-926: Improper Export of Android Application Components), allowing improperly exported Telephony interfaces to be queried by any installed app. No active exploitation is confirmed - EPSS sits at 0.15% (5th percentile) and the vulnerability is absent from CISA KEV - but the breadth of affected chipsets spanning budget through flagship tiers gives this issue significant deployment reach. Patch ALPS11086431 is available per MediaTek's August 2026 security bulletin.
RemediationAI
Apply patch ALPS11086431 as documented in MediaTek's August 2026 Product Security Bulletin at https://www.mediatek.com/product-security-bulletin/August-2026. Because MediaTek distributes patches to OEM and ODM partners rather than end users directly, affected device manufacturers must integrate this fix into their own security update releases - users should apply the next available OEM security patch for their device. As a compensating control prior to patch availability, organizations managing Android fleets (MDM/EMM deployments) can enforce application allowlisting to prevent untrusted or sideloaded applications from running, which would deny the local execution foothold required for exploitation. Restricting Android Unknown Sources installation and enforcing Google Play Protect narrows the threat surface for consumer devices. There are no known workarounds that address the missing permission check itself without the vendor-supplied patch.
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
CWE-926 describes improper export of Android application components - in practice, this means a Content Provider, BroadcastReceiver, Service, or Activity within the Telephony stack is exported in the Android manifest without enforcing a corresponding permission declaration or programmatic permission check. Android's Telephony subsystem manages subscriber identity (IMSI, MSISDN), call state, SMS/MMS metadata, network registration data, and SIM slot information - all sensitive data classes. The CPE string (cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:*) confirms the vulnerability is in MediaTek's proprietary Telephony extensions layered atop AOSP, not in upstream Android itself. The 42 affected chipsets span MediaTek's MT6700 and MT8000 series, covering LTE and 5G SoC families used across consumer Android devices.
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:N/UI:N/S:U/C:H/I:N/A:N
Local vector required since exploitation demands on-device app execution; PR:N confirmed because the exported component imposes no privilege check on callers; C:H reflects telephony subscriber data sensitivity; no integrity or availability impact.
Primary rating from Vendor (MediaTek).
CVSS VectorVendor: MediaTek
Lifecycle Timeline
3DescriptionCVE.org
In Telephony, there is a possible information disclosure due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11086431; Issue ID: MSV-8189.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in MediaTek Telephony Permission Bypass Vulnerabilities
View all 2More 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
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-52074
GHSA-673r-7q9g-8844
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB