CVE-2025-20795: CWE-787 Out-of-bounds Write in MediaTek, Inc. MT2718, MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6873, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8186, MT8188, MT8195, MT8196, MT8370, MT8390, MT8391, MT8395, MT8676, MT8678, MT8696, MT8755, MT8766, MT8768, MT8781, MT8786, MT8788E, MT8791T, MT8792, MT8793, MT8796, MT8873, MT8883, MT8893
CVE-2025-20795 is a high-severity out-of-bounds write vulnerability in MediaTek chipsets used in many Android devices from versions 13. 0 to 16. 0. It occurs in the KeyInstall component due to a missing bounds check, allowing a local attacker with System privileges to escalate privileges further without user interaction. Exploitation requires prior System-level access, but once exploited, it can compromise confidentiality, integrity, and availability of the device. The vulnerability affects a wide range of MediaTek SoCs commonly found in smartphones and IoT devices. No known exploits are currently in the wild, but patching is critical to prevent potential privilege escalation attacks. European organizations using devices with these chipsets should prioritize updates and monitor for suspicious local activity. Mitigation involves applying vendor patches promptly and restricting System-level access to trusted processes only.
AI Analysis
Technical Summary
CVE-2025-20795 is an out-of-bounds write vulnerability classified under CWE-787, affecting a broad spectrum of MediaTek chipsets including MT2718, MT6580, MT6739, MT6761, and many others. The flaw exists in the KeyInstall component, where a missing bounds check allows memory corruption through out-of-bounds writes. This vulnerability can be exploited locally by an attacker who already has System-level privileges on the device, enabling them to escalate privileges further, potentially gaining full control over the device. The vulnerability does not require user interaction, increasing its risk in environments where System privilege is attainable. The affected devices run Android versions 13.0 through 16.0, encompassing many modern smartphones and embedded devices using MediaTek SoCs. The CVSS v3.1 score of 7.8 reflects high severity, with high impact on confidentiality, integrity, and availability, and low attack complexity due to the local nature and lack of user interaction. Although no exploits are currently known in the wild, the broad range of affected chipsets and Android versions makes this a significant threat. The vulnerability was published in early 2026, with MediaTek assigning the issue ID MSV-5141 and patch ID ALPS10276761, though no direct patch links are provided in the data. The vulnerability’s exploitation could lead to complete device compromise, data leakage, or denial of service, especially in devices used in critical infrastructure or enterprise environments.
Potential Impact
For European organizations, the impact of CVE-2025-20795 can be substantial, particularly for those relying on Android devices powered by MediaTek chipsets for corporate communications, mobile workforce, or IoT deployments. Successful exploitation could allow attackers with local System access to escalate privileges, potentially leading to full device compromise, unauthorized data access, or disruption of services. This is especially critical for sectors such as finance, healthcare, and government, where device integrity and confidentiality are paramount. The vulnerability could also affect embedded systems in industrial control or smart city infrastructure that utilize these chipsets, increasing the risk of operational disruption. Given the widespread use of MediaTek SoCs in affordable smartphones popular in Europe, many employees’ personal devices could be vulnerable, raising the risk of lateral movement or data exfiltration within corporate networks. The lack of user interaction for exploitation means that once System access is gained, attackers can operate stealthily and efficiently. The absence of known exploits in the wild currently provides a window for proactive mitigation, but the potential for rapid weaponization remains high.
Mitigation Recommendations
European organizations should implement a multi-layered mitigation strategy beyond generic patching advice. First, they must inventory and identify all devices using affected MediaTek chipsets and Android versions 13.0 to 16.0 within their environment. Coordinate with device vendors and Mobile Device Management (MDM) providers to deploy the official MediaTek patch (ALPS10276761) as soon as it becomes available. Until patches are applied, restrict local System-level access by enforcing strict privilege separation and monitoring for privilege escalation attempts using endpoint detection and response (EDR) tools. Employ application whitelisting and integrity monitoring to detect anomalous behavior in the KeyInstall component or related processes. For IoT and embedded devices, isolate vulnerable devices on segmented networks to limit attack surface and lateral movement. Educate IT and security teams about the vulnerability’s characteristics to improve incident detection and response readiness. Regularly review logs for signs of out-of-bounds write exploitation attempts and anomalous memory corruption events. Finally, collaborate with vendors to obtain timely firmware updates and validate patch effectiveness through testing before wide deployment.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden, Belgium, Austria
CVE-2025-20795: CWE-787 Out-of-bounds Write in MediaTek, Inc. MT2718, MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6873, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8186, MT8188, MT8195, MT8196, MT8370, MT8390, MT8391, MT8395, MT8676, MT8678, MT8696, MT8755, MT8766, MT8768, MT8781, MT8786, MT8788E, MT8791T, MT8792, MT8793, MT8796, MT8873, MT8883, MT8893
Description
CVE-2025-20795 is a high-severity out-of-bounds write vulnerability in MediaTek chipsets used in many Android devices from versions 13. 0 to 16. 0. It occurs in the KeyInstall component due to a missing bounds check, allowing a local attacker with System privileges to escalate privileges further without user interaction. Exploitation requires prior System-level access, but once exploited, it can compromise confidentiality, integrity, and availability of the device. The vulnerability affects a wide range of MediaTek SoCs commonly found in smartphones and IoT devices. No known exploits are currently in the wild, but patching is critical to prevent potential privilege escalation attacks. European organizations using devices with these chipsets should prioritize updates and monitor for suspicious local activity. Mitigation involves applying vendor patches promptly and restricting System-level access to trusted processes only.
AI-Powered Analysis
Technical Analysis
CVE-2025-20795 is an out-of-bounds write vulnerability classified under CWE-787, affecting a broad spectrum of MediaTek chipsets including MT2718, MT6580, MT6739, MT6761, and many others. The flaw exists in the KeyInstall component, where a missing bounds check allows memory corruption through out-of-bounds writes. This vulnerability can be exploited locally by an attacker who already has System-level privileges on the device, enabling them to escalate privileges further, potentially gaining full control over the device. The vulnerability does not require user interaction, increasing its risk in environments where System privilege is attainable. The affected devices run Android versions 13.0 through 16.0, encompassing many modern smartphones and embedded devices using MediaTek SoCs. The CVSS v3.1 score of 7.8 reflects high severity, with high impact on confidentiality, integrity, and availability, and low attack complexity due to the local nature and lack of user interaction. Although no exploits are currently known in the wild, the broad range of affected chipsets and Android versions makes this a significant threat. The vulnerability was published in early 2026, with MediaTek assigning the issue ID MSV-5141 and patch ID ALPS10276761, though no direct patch links are provided in the data. The vulnerability’s exploitation could lead to complete device compromise, data leakage, or denial of service, especially in devices used in critical infrastructure or enterprise environments.
Potential Impact
For European organizations, the impact of CVE-2025-20795 can be substantial, particularly for those relying on Android devices powered by MediaTek chipsets for corporate communications, mobile workforce, or IoT deployments. Successful exploitation could allow attackers with local System access to escalate privileges, potentially leading to full device compromise, unauthorized data access, or disruption of services. This is especially critical for sectors such as finance, healthcare, and government, where device integrity and confidentiality are paramount. The vulnerability could also affect embedded systems in industrial control or smart city infrastructure that utilize these chipsets, increasing the risk of operational disruption. Given the widespread use of MediaTek SoCs in affordable smartphones popular in Europe, many employees’ personal devices could be vulnerable, raising the risk of lateral movement or data exfiltration within corporate networks. The lack of user interaction for exploitation means that once System access is gained, attackers can operate stealthily and efficiently. The absence of known exploits in the wild currently provides a window for proactive mitigation, but the potential for rapid weaponization remains high.
Mitigation Recommendations
European organizations should implement a multi-layered mitigation strategy beyond generic patching advice. First, they must inventory and identify all devices using affected MediaTek chipsets and Android versions 13.0 to 16.0 within their environment. Coordinate with device vendors and Mobile Device Management (MDM) providers to deploy the official MediaTek patch (ALPS10276761) as soon as it becomes available. Until patches are applied, restrict local System-level access by enforcing strict privilege separation and monitoring for privilege escalation attempts using endpoint detection and response (EDR) tools. Employ application whitelisting and integrity monitoring to detect anomalous behavior in the KeyInstall component or related processes. For IoT and embedded devices, isolate vulnerable devices on segmented networks to limit attack surface and lateral movement. Educate IT and security teams about the vulnerability’s characteristics to improve incident detection and response readiness. Regularly review logs for signs of out-of-bounds write exploitation attempts and anomalous memory corruption events. Finally, collaborate with vendors to obtain timely firmware updates and validate patch effectiveness through testing before wide deployment.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- MediaTek
- Date Reserved
- 2024-11-01T01:21:50.403Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 695c6e7a3839e44175bdd3dc
Added to database: 1/6/2026, 2:07:54 AM
Last enriched: 1/14/2026, 1:52:46 AM
Last updated: 2/7/2026, 11:08:54 AM
Views: 18
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2083: SQL Injection in code-projects Social Networking Site
MediumCVE-2026-2082: OS Command Injection in D-Link DIR-823X
MediumCVE-2026-2080: Command Injection in UTT HiPER 810
HighCVE-2026-2079: Improper Authorization in yeqifu warehouse
MediumCVE-2026-1675: CWE-1188 Initialization of a Resource with an Insecure Default in brstefanovic Advanced Country Blocker
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.