CVE-2025-20657: MediaTek MT6765, MT6768, MT6781, MT6789, MT6833, MT6853, MT6877, MT6885, MT8768, MT8771, MT8781, MT8786, MT8791T · Out-of-bounds Write
Affects MediaTek MT6765, MT6768, MT6781, MT6789, MT6833, MT6853, MT6877, MT6885, MT8768, MT8771, MT8781, MT8786, MT8791TSource CVE Database V5
Not known to be exploited · CVSS 6.7 Medium.
Data as of 26 Oct 2026, 12:55 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 7 Apr 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. MT6765, MT6768, MT6781, MT6789, MT6833, MT6853, MT6877, MT6885, MT8768, MT8771, MT8781, MT8786, MT8791T | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-20657, organizations and users should: 1) Apply official security patches from device manufacturers or MediaTek as soon as they become available, referencing patch ID ALPS09486425 and issue ID MSV-2609. 2) Monitor vendor advisories and update Android OS versions on affected devices promptly to incorporate fixes. 3) Limit the number of applications and processes granted System-level privileges to reduce the risk of initial compromise that could lead to exploitation. 4) Employ mobile device management (MDM) solutions to enforce security policies and restrict installation of untrusted apps that might escalate privileges. 5) Use runtime protection and behavioral monitoring tools to detect anomalous activities indicative of privilege escalation attempts. 6) For organizations deploying custom ROMs or firmware, ensure that the vdec component is updated and input validation is enforced rigorously. 7) Educate users about the risks of rooting or jailbreaking devices, which can increase exposure to such vulnerabilities. 8) Conduct regular security audits and penetration testing focused on privilege escalation vectors in mobile environments. These targeted actions go beyond generic advice by focusing on controlling System privilege access and ensuring timely patch deployment on affected MediaTek platforms.
Description
In vdec, there is a possible permission bypass due to improper input validation. 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: ALPS09486425; Issue ID: MSV-2609.