CVE-2025-20795: MediaTek chipset · Out-of-bounds Write
Affects MediaTek chipsetSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 14:05 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:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jan 2026
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.MediaTek chipset | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-20795, organizations and users should: 1) Monitor MediaTek and device vendor advisories closely for official patches or firmware updates addressing this vulnerability and apply them promptly once available. 2) Restrict local access to devices, especially preventing untrusted users from obtaining System-level privileges, through strong authentication and endpoint protection controls. 3) Employ application whitelisting and mobile device management (MDM) solutions to limit installation of unauthorized software that could facilitate privilege escalation. 4) Conduct regular security audits and monitoring for signs of privilege escalation or suspicious activity on devices using affected chipsets. 5) For device manufacturers and integrators, implement additional runtime protections such as memory safety checks and exploit mitigations in firmware. 6) Educate users about the risks of granting elevated privileges to untrusted applications or users. 7) Consider network segmentation and limiting device exposure to reduce the impact of potential compromises. These steps go beyond generic advice by focusing on controlling local privilege escalation vectors and preparing for patch deployment in embedded systems.
Description
In KeyInstall, 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: ALPS10276761; Issue ID: MSV-5141.