Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical device access
-
DeliveryConnect via hardware debug interface (USB/JTAG)
-
ExploitDeliver crafted input during secure boot phase
-
ExecutionTrigger heap buffer overflow in sec boot
-
PersistCorrupt boot verification logic or execution pointer
-
ImpactLoad unsigned or malicious firmware with elevated 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 | Physical access to the target device is the explicit, non-negotiable prerequisite - CVSS AV:P confirms this. The vulnerable process is secure boot (sec boot), which executes during early device initialization before the operating system is loaded, meaning exploitation must be performed via pre-OS interfaces such as USB fastboot, JTAG debug ports, or direct flash memory access. No software-level authentication is required (PR:N per CVSS), as the attacker operates at a firmware layer where OS-level access controls are not yet active. User interaction is not required (UI:N). Exploitation is limited to four specific chipset models: MT2737, MT6880, MT6890, and MT6990. Remote or network-based exploitation is categorically not possible. The primary limiting factors for defenders are: physical access controls on the device, bootloader lock enforcement by the OEM, and disabling hardware debug interfaces in production firmware. |
| Impact | The CVSS 3.1 vector AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yields a 6.1 score - moderate overall, but the high C and I sub-scores indicate full compromise of the boot trust chain is feasible once physical access is obtained. The physical attack vector (AV:P) is the dominant risk-limiting factor: this cannot be triggered remotely, over a network, or via any software-only path, which is directly reflected in the EPSS score of 0.16% at only the 6th percentile. No CISA KEV listing and no known public POC further confirm this has not transitioned to widespread exploitation. The absence of a scope change (S:U) indicates the attacker's impact is bounded to the vulnerable system itself rather than pivoting to adjacent infrastructure. Real-world priority is therefore moderate for device manufacturers and organizations with strict physical device security requirements (e.g., mobile device management fleets, IoT deployments), and low for cloud or server environments. The AC:L rating indicates no special timing or race condition is required once physical access is achieved, meaning exploitation is technically straightforward for a skilled attacker once the physical barrier is overcome. |
| Exploit ScenarioDerived | An attacker who obtains physical possession of a device running an affected MediaTek chipset - for example, through theft, a checkpoint inspection, or insider access - connects via a hardware debug interface such as USB in fastboot mode or JTAG to interact with the device before the OS loads. By supplying a specially crafted payload during the secure boot process, the attacker triggers the heap buffer overflow, corrupting boot verification state and bypassing the secure boot chain to load unsigned firmware or a malicious bootloader with elevated privileges. No public exploit code or proof-of-concept has been identified at the time of analysis, but the AC:L rating indicates no special conditions beyond physical access are required for a skilled attacker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Secure boot heap buffer overflow in MediaTek chipsets MT2737, MT6880, MT6890, and MT6990 enables local privilege escalation by an attacker with physical device access. The vulnerability exists at the pre-OS firmware layer, where a write beyond allocated heap boundaries can corrupt boot verification logic and permit execution of unsigned or attacker-controlled code. No active exploitation has been confirmed - the vulnerability is absent from CISA KEV, and the EPSS score of 0.16% (6th percentile) is consistent with the hard physical access prerequisite sharply limiting opportunistic exploitation.
RemediationAI
MediaTek has released patches identified as AUTO00845351 (specifically for MT2737) and ALPS11072643 (for MT6880, MT6890, and MT6990), documented in the August 2026 Product Security Bulletin at https://www.mediatek.com/product-security-bulletin/August-2026. OEMs integrating affected chipsets must incorporate these patches into their firmware builds and distribute OTA updates to end users; there is no version number independently confirmed for the patched firmware release, only the internal patch IDs. As a compensating control where OEM patches are pending, organizations managing device fleets should enforce strict physical access controls - locking devices, enforcing tamper-evident seals, disabling accessible debug interfaces (JTAG, fastboot unlock) where the OEM allows it, and tracking device custody chains. Disabling USB debugging and bootloader unlock on managed devices limits the attack surface, though the trade-off is reduced repairability and development utility.
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 vulnerable component is the secure boot (sec boot) subsystem embedded in MediaTek chipset firmware, confirmed via CPE cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:* across models MT2737, MT6880, MT6890, and MT6990. Secure boot is a firmware-level trust chain mechanism that cryptographically validates each bootloader stage before handing off execution; a flaw here operates entirely below the operating system. CWE-787 (Out-of-bounds Write) identifies the root cause as heap memory written beyond its allocated bounds, a class of vulnerability that can overwrite adjacent heap structures - in this context, potentially corrupting cryptographic verification state, function pointers, or boot policy flags used by the secure boot chain. Exploitation likely targets hardware debug or firmware-load interfaces (e.g., JTAG, USB fastboot, direct NAND flash) that are accessible prior to OS initialization.
Know when Mediatek Chipset 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:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Physical access required for pre-OS firmware exploitation; PR:N because software authentication is not active at secure boot stage; no availability impact as device hardware functionality is preserved.
Primary rating from Vendor (MediaTek).
CVSS VectorVendor: MediaTek
Lifecycle Timeline
2DescriptionCVE.org
In sec boot, there is a possible escalation of privilege due to a heap buffer overflow. This could lead to local escalation of privilege, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: AUTO00845351 (Note: For MT2737) / ALPS11072643 (Note: For MT6880, MT6890, MT6990); Issue ID: MSV-6929.
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.
More in Mediatek Chipset
View allOut-of-bounds write in MediaTek modem firmware enables remote privilege escalation when devices connect to attacker-cont
Heap buffer overflow in the vdec (video decoder) kernel driver across 53+ MediaTek SoCs allows a local unprivileged atta
Local privilege escalation in MediaTek's vdec (video decoder) kernel driver affects more than 53 distinct chipset varian
Heap-based buffer overflow in the MediaTek WLAN AP driver enables an adjacent-network attacker to escalate privileges wi
Out-of-bounds write in MediaTek modem chipset implementations allows remote privilege escalation when user equipment con
Heap buffer overflow in the MediaTek WLAN access point driver allows adjacent-network attackers with low-privilege user
Local privilege escalation in MediaTek's Bluetooth driver affects six Wi-Fi/Bluetooth combo chipsets (MT7902, MT7920, MT
Local privilege escalation in MediaTek GenieZone (trusted execution environment) allows an attacker who has already gain
Privilege escalation in MediaTek's Android Telephony component enables any locally-installed application - regardless of
Out-of-bounds read in MediaTek modem firmware across 19 chipsets enables remote denial of service when a User Equipment
Remote privilege escalation in the baseband modem firmware of dozens of MediaTek chipsets allows an attacker operating a
Privilege escalation via a double-free memory corruption bug in camera middleware affects 17 MediaTek chipset variants,
EUVD-2026-52056
GHSA-4fw3-96wh-rv55
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB