CVE-2026-20420: MediaTek chipset · Out-of-bounds Read
Affects MediaTek chipsetSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Feb 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MediaTek, Inc.MediaTek chipset | Affected
| Fixed in– |
AI-suggested
Organizations and device users should promptly apply the official MediaTek patch MOLY01738313 to affected devices to remediate the vulnerability. Network operators and security teams should monitor for and mitigate rogue base stations within their coverage areas using radio frequency monitoring tools and anomaly detection systems. Deploying network-level protections such as base station authentication and secure network protocols can reduce exposure. Device manufacturers and integrators should ensure firmware updates are delivered securely and promptly to end users. For critical deployments, consider using devices with chipsets not affected by this vulnerability or that have been patched. Network segmentation and limiting device exposure to untrusted networks can further reduce risk. Security teams should also educate users about the risks of connecting to unknown or suspicious cellular networks. Continuous monitoring for unusual device behavior indicative of denial of service conditions can enable faster incident response.
Description
In Modem, there is a possible system crash due to incorrect error handling. This could lead to remote denial of service, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01738313; Issue ID: MSV-5935.