LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20420: In Modem, there is a possible system crash due to incorrect error handling.

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-20420 affects listed MediaTek chipsets. A nearby attacker operating a rogue base station could crash the modem after a device connects, causing denial of service. It does not claim data theft or code execution. Business impact is service disruption for affected mobile or connected devices in hostile radio environments.

Executive priority

Treat as a moderate availability risk. Prioritize if your organization relies on affected MediaTek-based devices for field operations, critical communications, IoT, or travel in higher-risk locations. The main concern is disruption, not confirmed compromise.

Technical view

MediaTek describes incorrect error handling in Modem, associated with CWE-125, leading to possible system crash. CVSS 3.1 is 6.5: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Exploitation requires the UE to connect to an attacker-controlled rogue base station. Patch ID is MOLY01738313; Issue ID MSV-5935.

Likely exposure

Exposure is limited to devices using the listed MediaTek chipsets and modem firmware that has not received the vendor fix. The attack is not internet-routable; it requires proximity or radio adjacency and a rogue base station scenario.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. The described attacker needs no privileges or user interaction, but must control a rogue base station that the target UE connects to.

Researcher notes

Evidence is limited to the CVE record and MediaTek bulletin reference. The affected list is chipset-level, so product-level exposure depends on OEM implementation and firmware distribution. No public exploit status or detailed technical advisory is provided in the supplied sources.

Mitigation direction

  • Identify products using the listed MediaTek chipsets.
  • Check MediaTek and device OEM advisories for updates containing patch ID MOLY01738313.
  • Deploy validated modem/baseband firmware updates through normal OEM or carrier channels.
  • Prioritize exposed fleets operating in untrusted or high-risk radio environments.

Validation and detection

  • Inventory affected chipset models across managed mobile, IoT, and embedded assets.
  • Compare installed firmware against OEM release notes referencing CVE-2026-20420 or MOLY01738313.
  • Confirm vendor bulletin applicability for each device model and region.
  • Track remediation status for devices lacking OEM firmware availability.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-20420 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-20420Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MediaTek, Inc.MediaTek chipsetMT2735, MT2737, MT6813, MT6815, MT6833, MT6835, MT6853, MT6855, MT6858, MT6873, MT6875, MT6877, MT6878, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6891, MT6893, MT6895, MT6896, MT6897, MT6899, MT6980, MT6983, MT6985, MT6986, MT6989, MT6990, MT6991, MT6993, MT8676, MT8791unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.