Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain physical device access
-
DeliveryConnect via USB and trigger DA boot mode
-
ExploitSend crafted DA protocol payload
-
ExecutionTrigger out-of-bounds write in DA memory buffer
-
ImpactDevice crashes (local denial of service)
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 an absolute requirement, confirmed by CVSS AV:P. The attacker must place the device into Download Agent (DA) mode, a pre-boot diagnostic state triggered via USB connection and specific hardware key sequences - this is not accessible during normal device operation. No authentication is required once in DA mode (CVSS PR:N), and no user interaction is needed (UI:N). Exploitation is concretely limited by: physical possession of the device, ability to initiate DA boot mode (which may be further restricted by OEM-specific locked-bootloader implementations), and the impact ceiling of local denial of service only - no code execution, privilege escalation, or data exfiltration is possible per available data. Devices not physically accessible to the attacker and devices with DA mode disabled or restricted by OEM configuration are not exploitable. |
| Impact | The CVSS 3.1 vector AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yields a score of 4.6 (Medium), with the physical attack vector being the dominant risk-limiting factor. EPSS of 0.16% at the 6th percentile confirms very low empirical exploitation probability. SSVC classifies this as non-automatable with no known exploitation and only partial technical impact, all consistent with a physical-access-only, availability-only vulnerability. The CVE is absent from CISA KEV and no POC has been identified. The sole impact is availability - denial of service - with zero confidentiality or integrity consequence, meaning an attacker cannot extract data or execute code based on current data. Signals are internally consistent and present no conflict: this is a low real-world priority despite the memory corruption class (CWE-787). The primary threat actors are those with device possession such as device repair shops, border inspections, or insider access scenarios. |
| Exploit ScenarioDerived | An attacker with physical possession of a vulnerable MediaTek-powered device connects it via USB and uses hardware key combinations or platform-specific tooling to place the device into Download Agent mode at boot time. The attacker then transmits a specially crafted DA protocol message that triggers the out-of-bounds write, corrupting memory and causing the device to crash or become permanently unresponsive. No public exploit code is known to exist, and replicating this attack requires both physical access and knowledge of the DA protocol, making opportunistic exploitation unlikely. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Out-of-bounds write in the MediaTek Download Agent (DA) firmware component across eight chipset families allows an attacker with physical device access to trigger a local denial of service by sending a crafted payload while the device is in DA mode. Affected chipsets span mobile SoCs (MT6880, MT6890, MT6990, MT6988, MT6986, MT6813) and modem/automotive chipsets (MT2735, MT2737), broadening the potential device footprint across Android smartphones and connected vehicle platforms. No public exploit code exists, EPSS sits at the 6th percentile (0.16%), SSVC confirms no known exploitation, and the physical access prerequisite fundamentally constrains real-world risk.
RemediationAI
Device manufacturers (OEMs) should integrate MediaTek patch ALPS10991588 for products using MT6880, MT6890, MT6990, MT6988, MT6986, or MT6813 chipsets, and patch AUTO00851171 for products using MT2735 or MT2737, then distribute updated firmware to end users via OTA or carrier updates. Consult the MediaTek August 2026 Product Security Bulletin at https://www.mediatek.com/product-security-bulletin/August-2026 for integration guidance. As a compensating control for enterprise or fleet-managed devices pending patch deployment, enforce physical security policies: restrict unattended device access, apply tamper-evident seals to high-value assets, and where OEM tooling permits, disable or lock Download Agent mode in production device configurations to prevent unauthorized entry into DA boot mode. Disabling DA mode may affect legitimate repair workflows, so weigh operational impact against the low exploitation probability before applying.
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 DA (Download Agent) is a low-level MediaTek firmware subsystem used for device flashing and diagnostics, accessed via USB in a special pre-boot mode. CWE-787 (Out-of-bounds Write) identifies the root cause: a missing bounds check allows write operations to exceed an allocated memory buffer, corrupting memory and causing a denial-of-service condition. The affected products per CPE (cpe:2.3:a:mediatek,_inc.:mediatek_chipset:*:*:*:*:*:*:*:*) include MT6880, MT6890, MT6990, MT6988, MT6986, and MT6813 - mobile application processor SoCs - as well as MT2735 and MT2737, which serve modem and automotive use cases. The DA subsystem is distinct from the main OS runtime; this vulnerability is exploitable only when the device is placed into DA boot mode, not during normal operation.
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:N/I:N/A:H
Physical access required to reach DA mode (AV:P); only availability impact as OOB write causes device crash with no code execution or data exposure.
Primary rating from Vendor (MediaTek).
CVSS VectorVendor: MediaTek
Lifecycle Timeline
2DescriptionCVE.org
In DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS10991588 (Note: For MT6880, MT6890, MT6990, MT6988, MT6986, MT6813) / AUTO00851171 (Note: For MT2735, MT2737); Issue ID: MSV-7790.
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
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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-52060
GHSA-w9g5-vfpg-gh63
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB