Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain System privilege on device
-
ExploitInvoke vulnerable venc interface
-
ExecutionTrigger type confusion out-of-bounds write
-
ImpactEscalate to kernel-level privilege
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 attacker to already possess System-level privilege on an affected MediaTek-based device and local access to invoke the vulnerable venc (video encoder) component; there is no remote or network path (AV:L) and no user interaction is needed (UI:N). The primary limiting factor is the high authentication/privilege bar (PR:H) - an attacker must have already compromised the device to the System account, so this cannot be used for initial access and functions only as a post-compromise kernel escalation step. Affected scope is restricted to the specific MediaTek chipsets enumerated in the EUVD advisory (e.g., MT6768, MT6833, MT6877, MT8186, MT8188, MT8195, MT8196, and others) running the unpatched firmware prior to patch ALPS11383899. |
| Impact | This is a genuine but constrained vulnerability, not a high-urgency remote threat. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 6.7 Medium) is internally consistent with the description: exploitation is local only (AV:L), requires no user interaction (UI:N), and - critically - demands that the attacker already hold System-level privilege (PR:H). The description reinforces this: it explicitly states escalation is possible only 'if a malicious actor has already obtained the System privilege,' so this is a privilege-boundary crossing from System to kernel, not an initial foothold. No EPSS score, CISA KEV listing, POC, or SSVC decision data was provided in the input; on available signals this is 'no public exploit identified at time of analysis.' The absence of exploitation-probability data combined with the high privilege prerequisite means real-world risk is modest: it is valuable as the final link in a chain (post-exploitation kernel escalation) rather than a standalone widely-weaponizable flaw. Treat it as a patch-in-normal-cycle item for affected MediaTek-based Android fleets rather than an emergency, while noting that CVSS/description are fully aligned here with no conflicting signals to reconcile. |
| Exploit ScenarioDerived | An attacker who has already compromised a MediaTek-based Android device to the System privilege level (e.g., via a prior app or service compromise) invokes the vulnerable venc (video encoder) interface with crafted input that triggers a type confusion, causing an out-of-bounds write. No user interaction is required, and the memory corruption is leveraged to escalate from System to kernel-level privileges. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Local privilege escalation in MediaTek venc on multiple chipsets allows an attacker who already possesses System-level privileges to escalate to kernel-level code execution via a type confusion that leads to an out-of-bounds write. The vulnerability requires local access and high privileges (PR:H) with no user interaction, and no public exploit has been identified at the time of analysis. This is a post-compromise escalation step, not a remote or initial-access vector.
RemediationAI
Apply the vendor-released patch identified as ALPS11383899 from MediaTek, which resolves the type confusion and out-of-bounds write in venc. Because the vulnerability requires an attacker to already have System privileges, preventing initial compromise is critical; ensure devices are up to date with all security patches and monitor for suspicious local activity. No specific feature can be disabled to fully mitigate the risk without losing video encoding functionality, so patching is the primary remediation. For devices that cannot be immediately patched, restrict local access to trusted users and implement robust endpoint detection to catch post-exploitation behavior. Refer to the MediaTek advisory at https://www.mediatek.com/product-security-bulletin/October-2026 for the latest guidance and firmware updates.
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 venc, MediaTek's video encoding component, which is present in a wide range of MediaTek chipsets. The root cause is a type confusion error (CWE-787: Out-of-bounds Write) where the component fails to properly validate object types, leading to memory corruption. Exploitation allows an attacker with System privileges to write out of bounds and potentially execute code in the kernel context, thereby escalating privileges. The affected chipsets include MT6768, MT6833, MT6877, MT8186, MT8188, MT8195, MT8196, and others as listed in the EUVD advisory. The patch ID ALPS11383899 addresses this issue.
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 vector (AV:L) with no user interaction; PR:H because exploitation requires pre-existing System privilege, and the OOB write yields full C/I/A impact.
Primary rating from Vendor (mediatek).
CVSS VectorVendor: mediatek
Lifecycle Timeline
3DescriptionCVE.org
In venc, there is a possible out of bounds write due to type confusion. 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: ALPS11383899; Issue ID: MSV-9606.
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.
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.
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-92207
GHSA-f92j-xqqj-522r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB