Security readout for executives and security teams
Plain-English summary
CVE-2026-20422 is a MediaTek modem flaw that can crash an affected device when it connects to an attacker-controlled rogue base station. It is a denial-of-service issue, not a data theft or code execution issue based on the provided sources. Business urgency is highest for fleets using affected MediaTek chipsets in mobile, tablet, IoT, or embedded cellular devices.
Executive priority
Treat this as a moderate availability risk. It is not reported as actively exploited and requires rogue base-station proximity, but a successful attack could disrupt connectivity. Prioritize environments where cellular availability matters, especially IoT, field operations, transportation, and managed mobile fleets using affected MediaTek hardware.
Technical view
The issue is improper input validation in MediaTek modem firmware, mapped to CWE-617. The CVSS 3.1 score is 6.5 with adjacent attack vector, no privileges, no user interaction, and high availability impact. MediaTek lists Patch ID MOLY00827332 and Issue ID MSV-5919. Affected chipset models are explicitly listed in the CVE source bundle.
Likely exposure
Exposure is limited to devices using the listed MediaTek chipsets and within range of a rogue base station controlled by an attacker. Organizations may be exposed through employee phones, tablets, cellular IoT, vehicle systems, or embedded devices if they contain affected chipsets and lack the relevant vendor firmware update.
Exploitation context
The attacker must operate a rogue base station and cause a user equipment device to connect to it. The sources state no user interaction and no privileges are required. CISA KEV status is false in the source bundle, and no provided source states active exploitation.
Researcher notes
Evidence is limited to the CVE record and MediaTek bulletin reference. The source bundle does not provide detailed modem protocol conditions, proof-of-concept information, or OEM firmware mapping. Avoid assuming exploit maturity or device-level patch availability without OEM confirmation.
Mitigation direction
- Identify devices using the affected MediaTek chipset models listed in the advisory.
- Check MediaTek and device OEM advisories for firmware containing Patch ID MOLY00827332.
- Prioritize updates for cellular IoT, field devices, and high-availability mobile fleets.
- If no OEM update is available, ask the vendor for remediation timelines.
- Monitor affected fleets for unexplained modem resets or connectivity loss.
Validation and detection
- Inventory device models and map them to underlying MediaTek chipsets.
- Confirm whether OEM firmware references the February 2026 MediaTek bulletin or patch ID.
- Verify patch deployment through mobile device management or asset management records.
- Review telecom or device logs for recurring modem crashes where available.
- Track the CVE record and MediaTek bulletin for updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-617: 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 lookupCVE-2026-20422 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://corp.mediatek.com/product-security-bulletin/February-2026CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.