Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain System privilege on device
  2. Exploit
    Invoke vulnerable venc interface
  3. Execution
    Trigger type confusion out-of-bounds write
  4. Impact
    Escalate 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

MediaTek chipset MT6768
MediaTek chipset MT8189
MediaTek chipset MT6833
MediaTek chipset MT8793
MediaTek chipset MT8196
MediaTek chipset MT8668
MediaTek chipset MT6789
MediaTek chipset MT8186
MediaTek chipset MT8781
MediaTek chipset MT6855
MediaTek chipset MT8910
MediaTek chipset MT8195
MediaTek chipset MT8799
MediaTek chipset MT8678
MediaTek chipset MT8188
MediaTek chipset MT8676
MediaTek chipset MT8395
MediaTek chipset MT8391
MediaTek chipset MT2718
MediaTek chipset MT6877
MediaTek chipset MT8788E
MediaTek chipset MT6769
MediaTek chipset MT8367
MediaTek chipset MT8696
MediaTek chipset MT8792

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

Vendor (mediatek) PRIMARY 6.7 MEDIUM
AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 6.7 MEDIUM

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.

3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (mediatek).

CVSS VectorVendor: mediatek

Attack Vector
Local
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Oct 05, 2026 - 11:22 NVD
6.7 (MEDIUM)
CVE Published
Oct 05, 2026 - 02:16 cve.org
MEDIUM 6.7
CVE Published
Oct 05, 2026 - 02:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.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

EPSS Score
0.1%
Top 99% exploitable
Prevalence
High
MediaTek chipsets power a large share of Android smartphones and tablets
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
High
Technical Impact
Total

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

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

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

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

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

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

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

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

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

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

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy