MediaTek NeuroPilot EUVD-2026-92204

Exploitation requires the attacker to already have local code execution on an affected device - specifically the ability to reach the MediaTek NeuroPilot (APU/AI) driver interface, typically via a malicious or compromised unprivileged Android application. Per the CVSS vector (AV:L/PR:N/UI:N), no special privileges and no user interaction are needed once that local app context exists, and it affects the listed MediaTek chipsets (MT8781, MT8189, MT6993, MT8793, MT8910, MT8668, MT8188, MT6881, MT8875) on firmware predating patch ALPS11249062. The principal limiting factor is the local attack vector: the flaw is not remotely reachable over a network and serves as a privilege-escalation step rather than an initial compromise, so devices without an attacker-controlled local process are not directly at risk from this issue alone.

This is a genuine high-priority patch target for affected MediaTek-based devices, though not an emergency on the scale of a remote-code-execution flaw. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U, C:H/I:H/A:H, score 8.4) describes a local, low-complexity out-of-bounds write (CWE-787) requiring no privileges and no user interaction, yielding full confidentiality, integrity, and availability impact via local privilege escalation. The AV:L constraint is the key risk limiter: an attacker must already be able to run code on the device (e.g., a malicious or compromised app), so this is a post-foothold escalation primitive rather than an initial access vector - consistent with the description's 'local escalation of privilege with no additional execution privileges needed.' No EPSS score was provided in the input, and there is no CISA KEV listing and no public POC referenced, so there is no evidence of active exploitation or weaponization at this time. The real-world weight comes from prevalence (MediaTek powers a very large share of Android devices) combined with the NeuroPilot AI/APU driver stack being reachable from unprivileged app context; memory-corruption bugs in such driver surfaces are historically attractive for Android LPE chains. Net: prioritize for patch rollout on affected chipsets, but the local-only vector means it is not a drop-everything remote threat.

A malicious or compromised Android application installed on a device using an affected MediaTek chipset invokes the NeuroPilot APU/AI interface with crafted parameters that bypass a missing bounds check, triggering an out-of-bounds write. By controlling the write, the attacker corrupts privileged memory to escalate from an unprivileged app context to elevated (kernel/system) privileges without any user interaction. No public exploit code has been identified at time of analysis, so a working exploit would need to be developed.