Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Android System privilege on device
-
ExploitInvoke unprotected aidl interface
-
ExecutionBypass missing permission check
-
ImpactEscalate to higher privilege with full device control
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: 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 that the attacker has ALREADY obtained the Android System privilege on the local device - this is the explicit precondition stated in the description and reflected by PR:H in the CVSS vector. The flaw is a missing permission check in the aidl component reachable from that System context; no user interaction is required (UI:N). Limiting factors: attack is local only (AV:L, no remote vector), there is no network-facing exposure, and the high System-privilege prerequisite means a standalone unprivileged app cannot trigger it directly - it is most relevant as the second stage of an exploit chain or for already-privileged malware. Affects MediaTek chipsets including MT6993, MT8188, MT6881, MT8793, MT6991, MT8668, MT6899, MT6989, MT8189, MT8781, MT6878, and MT8910. |
| Impact | This is a moderate, defense-in-depth issue rather than a top-tier emergency. The provided CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U) and the description agree and reinforce each other: exploitation is local only and requires that the attacker ALREADY hold the System privilege (PR:H), after which a missing permission check (CWE-862) in aidl permits further escalation with full C:H/I:H/A:H impact on the device. No EPSS score, CISA KEV listing, POC, or SSVC decision data was supplied in the input. There is no CISA KEV entry, so this is NOT confirmed as actively exploited. The high PR requirement is the dominant mitigating signal - an attacker must first compromise a highly privileged (System) context, which substantially narrows the realistic attacker population to malware or a chained exploit that has already achieved System access. The 6.7 base score is consistent with 'serious if reached, but gated behind a significant precondition.' No signals conflict; the main gap is the absence of exploitation-probability (EPSS) and exploit-availability data, so prioritization should treat this as a routine patch-cycle item unless the device is part of a threat model where System-level compromise is plausible. |
| Exploit ScenarioDerived | Malware or a previously-chained exploit that has already gained the Android System privilege on a MediaTek-powered device invokes an aidl interface that fails to perform a required permission check. Because no user interaction is needed, the code silently escalates from System to a higher-privileged context, gaining full read/write/availability control. No public exploit was identified in the provided data, so this reflects the attack path implied by the CVSS vector and description rather than a demonstrated exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
A missing permission check in the MediaTek AIDL (Android Interface Definition Language) component allows an attacker who already holds the Android System privilege to escalate to higher privileges locally, with no user interaction required. The expected impact is high across confidentiality, integrity, and availability (CVSS 3.1 base 6.7, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), but the local-only vector and the PR:H precondition mean an ordinary unprivileged app cannot trigger it directly - it is only useful as a second-stage step in an existing exploit chain or for already-privileged malware. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); this is a moderate, defense-in-depth issue rather than a top-tier emergency.
RemediationAI
Patch available per vendor advisory: apply the MediaTek October 2026 Product Security Bulletin fix identified by Patch ID ALPS11185216 (issue MSV-9039) - because this is chipset firmware/system-component code, the practical route is the device OEM's Android security update, so users should install the latest OEM build containing the October 2026 MediaTek bulletin level and enterprises should require that bulletin level in their device compliance baseline. No vendor-published mitigation is provided beyond the patch, and there is no exact patched version number in the available data. If patching cannot be applied immediately, compensating controls must target the PR:H precondition rather than the interface itself: enforce strict app-privilege hygiene so nothing beyond trusted platform code runs with System privilege (block sideloading of privileged apps, restrict which OEM/preinstalled apps hold android:sharedUserId="android.uid.system"), and use MDM/Play Integrity checks to detect tampered or rooted builds that could grant System context - the trade-off is reduced device flexibility and, in some fleets, blocked line-of-business sideloaded tooling. Note that because the attack is local and already requires System privilege, these controls lower the chance of a chain reaching the vulnerable AIDL call but do not substitute for the firmware 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
AIDL is the Android Interface Definition Language used to define Binder-based IPC interfaces between Android system services and their clients; the vulnerable code path lives in a MediaTek-supplied AIDL service that is reachable from the Android System context. The root cause is CWE-862 (Missing Authorization): the interface fails to verify that the caller holds the permission required prior to performing a privileged operation, so any process already running with System-level privilege can invoke functionality it should not be able to. The CVSS vector's PR:H reflects the explicit precondition in the description that the actor has already obtained the System privilege, and AV:L/UI:N confirm this is a local, non-interactive attack with no network-facing exposure. The affected implementations span a broad set of MediaTek SoCs (MT6993, MT8188, MT6881, MT8793, MT6991, MT8668, MT6899, MT6989, MT8189, MT8781, MT6878, MT8910), which means the issue is vendor-firmware dependent rather than tied to a single Android release.
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:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Local-only escalation (AV:L) requiring the attacker to already hold the System privilege (PR:H) with no user interaction (UI:N); missing permission check yields full C/I/A impact within the same scope.
Primary rating from Vendor (mediatek).
CVSS VectorVendor: mediatek
Lifecycle Timeline
3DescriptionCVE.org
In aidl, there is a possible escalation of privilege due to a missing permission check. 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: ALPS11185216; Issue ID: MSV-9039.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Related Vulnerabilities in MediaTek aidl Use-After-Free and Permission Flaws
View all 3Adobe 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-92188
GHSA-8mmg-g9gw-84mh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB