CVE-2025-20774: MediaTek MT2718, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793 · Heap Overflow
Affects MediaTek MT2718, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793Source CVE Database V5
Not known to be exploited · CVSS 6.7 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MediaTek, Inc. MT2718, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6877, MT6878, MT6879, MT6883, MT6885, MT6886, MT6889, MT6893, MT6895, MT6897, MT6899, MT6983, MT6985, MT6989, MT6991, MT8196, MT8676, MT8678, MT8792, MT8793 | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-20774, organizations and device manufacturers should prioritize applying the official MediaTek patch ALPS10196993 as soon as it becomes available. Until patches are deployed, enforcing strict privilege separation and minimizing the number of processes or applications running with System-level privileges can reduce exploitation risk. Employing runtime protections such as heap integrity checks, address space layout randomization (ASLR), and control-flow integrity (CFI) can help detect or prevent exploitation attempts. Device administrators should audit and restrict applications or services that can escalate to System privileges, and monitor for suspicious local activity indicative of privilege escalation attempts. For enterprises deploying MediaTek-based devices, consider endpoint detection and response (EDR) solutions capable of identifying anomalous behavior related to heap overflows or privilege escalations. Regularly update device firmware and Android OS versions to incorporate security fixes. Finally, educating users and administrators about the risks of granting elevated privileges to untrusted applications can help reduce the initial access vector.
Description
In display, 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: ALPS10196993; Issue ID: MSV-4796.