CVE-2025-20800: 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-20800, organizations and device manufacturers should: 1) Apply the official patch from MediaTek (ALPS10267349) as soon as it becomes available to ensure the bounds check is properly implemented. 2) Restrict local access to devices running affected chipsets by enforcing strict access controls and monitoring for unauthorized privilege escalations. 3) Implement robust privilege separation and minimize the number of processes running with System-level privileges to reduce the attack surface. 4) Employ runtime protections such as memory protection mechanisms (e.g., DEP, ASLR) to hinder exploitation of out-of-bounds writes. 5) Monitor device logs and behavior for anomalies indicative of exploitation attempts, especially local privilege escalation activities. 6) For organizations deploying these chipsets in critical environments, consider network segmentation and endpoint detection solutions to detect and contain potential compromises. 7) Educate users and administrators about the risks of local privilege escalation vulnerabilities and the importance of timely patching. These steps go beyond generic advice by focusing on access control, runtime protections, and proactive monitoring tailored to the nature of this vulnerability.
Description
In mminfra, 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: ALPS10267349; Issue ID: MSV-5033.