CVE-2026-20412: CWE-787 Out-of-bounds Write in MediaTek, Inc. MT6878, MT6879, MT6881, MT6886, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT6993, MT8168, MT8188, MT8195, MT8365, MT8390, MT8395, MT8666, MT8667, MT8673, MT8676, MT8696, MT8793
In cameraisp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10351676; Issue ID: MSV-5733.
AI Analysis
Technical Summary
CVE-2026-20412 is an out-of-bounds write vulnerability classified under CWE-787 found in the cameraisp component of MediaTek, Inc.'s system-on-chip (SoC) products, including MT6878 through MT8793 series. The vulnerability stems from a missing bounds check in the cameraisp code, which can lead to memory corruption via out-of-bounds write operations. This flaw allows a local attacker who already has System-level privileges on the device to escalate their privileges further, potentially gaining higher-level control over the device. The vulnerability does not require user interaction to be exploited, increasing its risk profile. It affects devices running Android versions 13.0 through 16.0 that incorporate the vulnerable MediaTek chipsets. The CVSS v3.1 base score is 7.8, indicating a high severity with high impact on confidentiality, integrity, and availability. The attack vector is local with low complexity and requires privileges but no user interaction. Although no exploits are currently known in the wild, the vulnerability poses a significant risk due to the widespread use of MediaTek SoCs in smartphones and IoT devices globally. The issue was reserved in November 2025 and published in February 2026, with patches identified by MediaTek under Patch ID ALPS10351676 and Issue ID MSV-5733. The vulnerability's exploitation could allow attackers to bypass security controls, manipulate sensitive data, or disrupt device functionality.
Potential Impact
The vulnerability could have severe impacts on affected devices and organizations relying on them. Successful exploitation allows a local attacker with System privileges to escalate their access, potentially gaining root or kernel-level control. This could lead to unauthorized access to sensitive data, modification or deletion of critical system files, installation of persistent malware, or disruption of device operations. For organizations, this could mean compromised mobile endpoints, leading to data breaches, espionage, or sabotage. The broad range of affected MediaTek chipsets means a large number of consumer and enterprise devices are at risk, especially smartphones and IoT devices using these SoCs. The lack of user interaction requirement increases the risk of automated or stealthy attacks. Although exploitation requires existing System privileges, attackers who gain such access through other means could leverage this vulnerability to fully compromise the device. This elevates the overall threat landscape and could impact privacy, data integrity, and service availability on a large scale.
Mitigation Recommendations
To mitigate this vulnerability effectively, organizations and users should: 1) Apply the official patches released by MediaTek (Patch ID ALPS10351676) as soon as they become available to ensure the bounds check is implemented correctly. 2) Restrict and monitor access to System-level privileges on devices to prevent attackers from obtaining the prerequisite access needed for exploitation. 3) Employ runtime protection mechanisms such as memory protection and integrity checks to detect and prevent out-of-bounds memory writes. 4) Implement strict application sandboxing and privilege separation to limit the impact of any privilege escalation. 5) Regularly update device firmware and operating systems to incorporate security fixes. 6) Monitor device logs and behavior for signs of privilege escalation attempts or anomalous activity related to cameraisp or MediaTek components. 7) For enterprises, enforce mobile device management (MDM) policies that restrict installation of untrusted applications and enforce security baselines. 8) Educate users and administrators about the risks of privilege escalation vulnerabilities and the importance of timely patching. These steps go beyond generic advice by focusing on controlling System privilege access and leveraging layered defenses.
Affected Countries
United States, China, India, Indonesia, Brazil, Russia, Germany, Japan, South Korea, Vietnam, Philippines, Thailand, Malaysia, Mexico, United Kingdom
CVE-2026-20412: CWE-787 Out-of-bounds Write in MediaTek, Inc. MT6878, MT6879, MT6881, MT6886, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT6993, MT8168, MT8188, MT8195, MT8365, MT8390, MT8395, MT8666, MT8667, MT8673, MT8676, MT8696, MT8793
Description
In cameraisp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10351676; Issue ID: MSV-5733.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-20412 is an out-of-bounds write vulnerability classified under CWE-787 found in the cameraisp component of MediaTek, Inc.'s system-on-chip (SoC) products, including MT6878 through MT8793 series. The vulnerability stems from a missing bounds check in the cameraisp code, which can lead to memory corruption via out-of-bounds write operations. This flaw allows a local attacker who already has System-level privileges on the device to escalate their privileges further, potentially gaining higher-level control over the device. The vulnerability does not require user interaction to be exploited, increasing its risk profile. It affects devices running Android versions 13.0 through 16.0 that incorporate the vulnerable MediaTek chipsets. The CVSS v3.1 base score is 7.8, indicating a high severity with high impact on confidentiality, integrity, and availability. The attack vector is local with low complexity and requires privileges but no user interaction. Although no exploits are currently known in the wild, the vulnerability poses a significant risk due to the widespread use of MediaTek SoCs in smartphones and IoT devices globally. The issue was reserved in November 2025 and published in February 2026, with patches identified by MediaTek under Patch ID ALPS10351676 and Issue ID MSV-5733. The vulnerability's exploitation could allow attackers to bypass security controls, manipulate sensitive data, or disrupt device functionality.
Potential Impact
The vulnerability could have severe impacts on affected devices and organizations relying on them. Successful exploitation allows a local attacker with System privileges to escalate their access, potentially gaining root or kernel-level control. This could lead to unauthorized access to sensitive data, modification or deletion of critical system files, installation of persistent malware, or disruption of device operations. For organizations, this could mean compromised mobile endpoints, leading to data breaches, espionage, or sabotage. The broad range of affected MediaTek chipsets means a large number of consumer and enterprise devices are at risk, especially smartphones and IoT devices using these SoCs. The lack of user interaction requirement increases the risk of automated or stealthy attacks. Although exploitation requires existing System privileges, attackers who gain such access through other means could leverage this vulnerability to fully compromise the device. This elevates the overall threat landscape and could impact privacy, data integrity, and service availability on a large scale.
Mitigation Recommendations
To mitigate this vulnerability effectively, organizations and users should: 1) Apply the official patches released by MediaTek (Patch ID ALPS10351676) as soon as they become available to ensure the bounds check is implemented correctly. 2) Restrict and monitor access to System-level privileges on devices to prevent attackers from obtaining the prerequisite access needed for exploitation. 3) Employ runtime protection mechanisms such as memory protection and integrity checks to detect and prevent out-of-bounds memory writes. 4) Implement strict application sandboxing and privilege separation to limit the impact of any privilege escalation. 5) Regularly update device firmware and operating systems to incorporate security fixes. 6) Monitor device logs and behavior for signs of privilege escalation attempts or anomalous activity related to cameraisp or MediaTek components. 7) For enterprises, enforce mobile device management (MDM) policies that restrict installation of untrusted applications and enforce security baselines. 8) Educate users and administrators about the risks of privilege escalation vulnerabilities and the importance of timely patching. These steps go beyond generic advice by focusing on controlling System privilege access and leveraging layered defenses.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- MediaTek
- Date Reserved
- 2025-11-03T01:30:59.008Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 69806094f9fa50a62f0b3fc2
Added to database: 2/2/2026, 8:30:12 AM
Last enriched: 2/27/2026, 7:52:43 AM
Last updated: 3/24/2026, 12:50:51 AM
Views: 53
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.