Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRun unprivileged code on device
-
ExploitSend crafted request to neuropilot
-
ExecutionTrigger out-of-bounds write via missing bounds check
-
ImpactCorrupt memory and escalate to system privileges
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 local code execution on a device using one of the affected MediaTek chipsets (MT8668, MT8875, MT8781, MT8910, MT6881, MT8188, MT8189, MT6993) with the vulnerable neuropilot component present - typically a locally installed or already-running Android application. Per the CVSS vector (AV:L), it cannot be triggered remotely over a network; the attacker must first have a foothold on the device. On the positive side, PR:N and UI:N mean that once local code runs, no elevated privileges and no user interaction are needed to trigger the out-of-bounds write. The primary limiting factors are the local-access prerequisite and dependence on the specific affected chipset/firmware being present and unpatched. |
| Impact | This is a genuine high-priority local escalation-of-privilege flaw, though not a drop-everything emergency on the raw signals available. The vendor-supplied CVSS:3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.4) is internally consistent with the description: an out-of-bounds write (CWE-787) in the MediaTek 'neuropilot' NPU/AI component that an unprivileged local actor can trigger with no user interaction, yielding full confidentiality, integrity and availability impact on the affected system. The local attack vector (AV:L) is the single most important risk-limiting factor - an attacker must already be able to run code on the device (e.g., a malicious or compromised app), so this is a privilege-escalation primitive rather than a remote entry point. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The CVE is NOT listed in CISA KEV and no POC was indicated, so the status is no public exploit identified at time of analysis; MediaTek credits its own security team (security@mediatek.com), consistent with internal discovery rather than observed in-the-wild abuse. Net: a real patch-worthy bug for Android/MediaTek fleets (especially as a second-stage privilege gain in an exploit chain), but with no evidence of active or widespread exploitation at this time. |
| Exploit ScenarioDerived | A user installs a malicious or trojanized Android app that requires no special permissions. The app issues crafted requests to the vulnerable neuropilot interface, triggering the missing bounds check to perform an out-of-bounds write that corrupts memory and elevates the app's privileges to system/kernel level. No public exploit code was identified, and the local attack vector means the attacker must already have code execution on the device. |
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's NeuroPilot component allows an attacker with an existing foothold on a device to corrupt memory and elevate privileges via an out-of-bounds write caused by a missing bounds check (CWE-787), rated CVSS 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Affected platforms are devices built on MediaTek chipsets MT8668, MT8875, MT8781, MT8910, MT6881, MT8188, MT8189 and MT6993 that ship an unpatched NeuroPilot build. The flaw is not remotely reachable and requires local code execution (typically a running or installed Android app with no special privileges); no user interaction or elevated permissions are needed once that foothold exists, and no public exploit code was identified at time of analysis.
RemediationAI
Apply the MediaTek fix identified by patch ID ALPS11249050 (issue MSV-9172), which OEMs must integrate into their device firmware; consult the MediaTek October 2026 product security bulletin at https://www.mediatek.com/product-security-bulletin/October-2026 and your device vendor's own security bulletin for the released build number, since no public version string is published for the chipset-level patch. Until an OEM update is available, the realistic mitigation is reducing attack surface for local code execution: restrict sideloading and untrusted app installation, enforce Google Play Protect and app-permission hardening, and keep the rest of the platform patched to shrink the pool of initial local exploits an attacker needs as a prerequisite, accepting that these are compensating controls and do not remove the underlying out-of-bounds write. On managed fleets or developer units, blocking the ability to run untrusted native code and monitoring for anomalous APU/NPU driver activity can lower exposure; retiring or segmenting devices that are past their OEM support window is the only way to fully eliminate the risk where ALPS11249050 will never be delivered.
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
NeuroPilot is MediaTek's AI/neural-processing software stack that spans the APU/NPU driver and related runtime interfaces on the vendor's Android SoCs, so it sits in a privileged, kernel-adjacent context that makes flaws there attractive for privilege escalation. The root cause is a missing bounds check before a write, classified as CWE-787 (Out-of-bounds Write) - an attacker-controlled length or index is used without validation, so data is written past the end of an allocated buffer and can overwrite adjacent memory such as control structures, function pointers or kernel objects. The CVSS vector confirms scope-unchanged, local attack (AV:L), low complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and high impact to confidentiality, integrity and availability (C:H/I:H/A:H); MediaTek tracks the fix under patch ID ALPS11249050 and issue ID MSV-9172.
Know when Mt8781 Firmware 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:H/A:H
Local app can trigger the OOB write with no privileges or interaction (AV:L/AC:L/PR:N/UI:N), and privilege escalation gives full system compromise (C:H/I:H/A:H, scope unchanged).
Primary rating from Vendor (mediatek).
CVSS VectorVendor: mediatek
Lifecycle Timeline
3DescriptionCVE.org
In neuropilot, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11249050; Issue ID: MSV-9172.
Executive ViewAI
A high-severity memory-corruption flaw in MediaTek's NeuroPilot component affects devices built on eight MediaTek chipset families (MT8668, MT8875, MT8781, MT8910, MT6881, MT8188, MT8189 and MT6993) running an unpatched NeuroPilot build, and there is currently no vendor-released fix. Any locally installed application - needing no elevated permissions and no user interaction - can leverage the flaw to gain full control of the device, meaning a single low-privilege app is sufficient to compromise the host. Leadership should care because these chipsets span both consumer Android endpoints and embedded/automotive platforms, so the exposure is fleet-wide and open-ended until MediaTek ships a patch, at which point remediation will require coordination with device OEMs rather than a simple internal update.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce application allowlisting and block sideloaded/untrusted apps via MDM to limit the local foothold required; disable or remove the NeuroPilot component on devices where it is not operationally required; monitor endpoints for memory-corruption or crash indicators associated with the component; segment high-value embedded and automotive deployments; and escalate to MediaTek and the device OEM for patch status and interim guidance.
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.
Related Vulnerabilities in MediaTek neuropilot Out-of-Bounds Write Flaws
View all 2More in Mt8781 Firmware
View allOut-of-bounds write in MediaTek's 'vdec' hardware video-decoder path allows remote escalation of privilege on a broad se
Local privilege escalation in MediaTek's APU (AI Processing Unit) allows a locally-executing attacker to corrupt memory
Local privilege escalation in MediaTek's Video HAL lets an unprivileged app already running on an affected device corrup
Local privilege escalation in the MediaTek APU (AI Processing Unit) driver allows an attacker with existing code executi
Local privilege escalation in MediaTek's meta component affects numerous MediaTek chipsets (including MT6789, MT6895, MT
Local privilege escalation in MediaTek venc on multiple chipsets allows an attacker who already possesses System-level p
Local privilege escalation in MediaTek's mtee (MediaTek TEE) allows an attacker who already holds System privilege to ex
Local privilege escalation in MediaTek mtee allows a local attacker who already holds Android System privilege to exploi
Local privilege escalation in MediaTek's vdec (video decoder) component allows an attacker who already holds System priv
Local privilege escalation in MediaTek AIDL on affected chipsets is possible via a use-after-free memory corruption, but
Local privilege escalation in the aidl component shipped on a defined set of MediaTek chipsets (MT6899, MT6991, MT8910,
EUVD-2026-92205
GHSA-49pr-gv6j-5p2c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB