CVE-2026-20440: MediaTek chipset · Specified Index, Position, or Offset
Affects MediaTek chipsetSource CVE Database V5
Not known to be exploited · CVSS 6.7 Medium.
Data as of 30 Oct 2026, 11:52 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 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MediaTek, Inc.MediaTek chipset | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-20440, organizations should prioritize the following actions: 1) Apply vendor-provided patches or firmware updates as soon as they become available, referencing Patch ID ALPS10431968 and Issue ID MSV-5824 for tracking. 2) Implement strict access controls and privilege separation to minimize the number of users or processes with System-level privileges, reducing the attack surface. 3) Employ runtime protection mechanisms such as memory protection and integrity monitoring to detect and prevent out-of-bounds writes. 4) Conduct regular security audits and vulnerability assessments on devices using MediaTek chipsets to identify potential exploitation attempts. 5) For IoT and embedded devices, ensure secure boot and firmware validation to prevent unauthorized code execution. 6) Monitor device logs and network traffic for unusual activity indicative of privilege escalation attempts. 7) Educate system administrators and developers about the risks associated with local privilege escalation vulnerabilities and the importance of timely patching. These targeted measures go beyond generic advice by focusing on controlling privilege levels and enhancing detection capabilities specific to the nature of this vulnerability.
Description
In MAE, 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: ALPS10431968; Issue ID: MSV-5824.