Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deploy rogue base station near target
  2. Delivery
    Induce victim UE to attach
  3. Exploit
    Send crafted modem signaling message
  4. Execution
    Trigger out-of-bounds access (missing bounds check)
  5. Impact
    Crash baseband modem (denial of service)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Array index validation
Exploitation Conditions

Exploitation is gated by Adjacent-network radio access: the attacker must operate a rogue/false base station within cellular radio range and the target UE must attach to it before the malformed modem message can be delivered - this is the exact 'if a UE has connected to a rogue base station controlled by the attacker' condition in the advisory and is why AC is High. No authentication is required (PR:N) and no user interaction is needed (UI:N), but the practical limiting factors are significant: physical/RF proximity, the operational effort of standing up a convincing rogue cell per target, and the fact that impact is confined to a modem crash (availability only). It is not remotely exploitable over the internet and does not affect default configurations reachable from a network path.

Impact

This is a medium-severity (CVSS 5.3) availability-only issue, and multiple signals agree it is NOT a top-tier priority despite the 'remote' framing. The CVSS vector CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H confirms impact is limited to availability (A:H) with no confidentiality or integrity effect, and critically the attack vector is Adjacent (AV:A) with High attack complexity (AC:H) - not truly 'network' reachable from the internet. The description reconciles this: exploitation requires the victim UE to first connect to a rogue base station the attacker controls, which is precisely why AC is High and AV is Adjacent rather than Network. No EPSS score was supplied, so exploitation probability cannot be quantified; there is no CISA KEV listing and no public POC referenced, so this is not actively exploited. SSVC-style reasoning: exploitation=none observed, automatable=no (requires physical radio proximity and a rogue cell per target), technical impact=partial (DoS/crash only). The practical risk is a localized, targeted radio-proximity denial of service (baseband/modem crash), not a scalable remote compromise. No conflicting signals of note - the CVSS vector and description are consistent; the main caveat is the absence of EPSS data to confirm the low real-world exploitation likelihood implied by the other metrics.

Exploit ScenarioDerived

An attacker stands up a rogue cellular base station (false cell) in physical radio range of a target device and induces the victim UE to attach to it. The attacker then sends crafted signaling/modem messages that hit a missing bounds check (CWE-129, improper array index validation), crashing the baseband modem and denying cellular service. No public exploit code has been identified, and the attack requires proximity plus a controlled rogue cell, making it targeted rather than mass-scalable.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 05, 2026

Denial of service in MediaTek cellular modem firmware lets an attacker running a rogue base station crash the modem of an attached device by delivering a malformed message that triggers a missing bounds check, severing cellular connectivity until the modem restarts. The flaw is availability-only (CVSS 5.3, AV:A/AC:H/PR:N/UI:N/C:N/I:N/A:H) and is gated by radio proximity plus the victim UE actually attaching to the attacker-controlled cell, so it is not reachable over the internet and carries no confidentiality or integrity impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, and MediaTek has shipped fixes (patch IDs MOLY01864925 / MOLY01210562) covering more than 50 chipsets across the October 2026 product security bulletin.

RemediationAI

MediaTek has released fixes for this issue under patch IDs MOLY01864925 / MOLY01210562 (issue MSV-8303), referenced from the MediaTek Product Security Bulletin for October 2026 at https://www.mediatek.com/product-security-bulletin/October-2026. Because the vulnerable code lives in the baseband of the SoC, the patch is delivered by the silicon vendor to device OEMs and then distributed as a full device firmware/security OTA, so the practical action is to apply the latest OEM security update for any device built on an affected MT-series chipset and to push that update to managed fleets - there is no end-user-installable modem-only patch. Where patching cannot be done immediately, the effective compensating control is reducing exposure to rogue base stations: disable legacy radio access technologies that are trivially impersonated (notably 2G and, if policy allows, 3G), and where the device or MDM supports it restrict network selection to trusted/home PLMN lists or disable automatic attach to unknown cells. The trade-off is clear - disabling 2G/3G removes fallback coverage in areas without 4G/5G, and strict PLMN locking breaks roaming and can leave devices without service in visited networks, so these should be scoped to high-value or stationary deployments. Do not rely on network-perimeter controls (firewalls, WAFs) since the attack never traverses an IP path, and note that no public exploit code has been identified, so these measures are precautionary rather than incident-driven.

Affected VersionsENISA

MediaTek chipset MT6885
MediaTek chipset MT6896
MediaTek chipset MT6877
MediaTek chipset MT6878
MediaTek chipset MT8791
MediaTek chipset MT2737
MediaTek chipset MT2716
MediaTek chipset MT6835
MediaTek chipset MT6986
MediaTek chipset MT8893
MediaTek chipset MT6855
MediaTek chipset MT6873
MediaTek chipset MT6883
MediaTek chipset MT6982
MediaTek chipset MT8755
MediaTek chipset MT8796
MediaTek chipset MT8775
MediaTek chipset MT8791T
MediaTek chipset MT8676
MediaTek chipset MT6879
MediaTek chipset MT6991
MediaTek chipset MT6891
MediaTek chipset MT6893
MediaTek chipset MT6813
MediaTek chipset MT6985
MediaTek chipset MT8792
MediaTek chipset MT6993
MediaTek chipset MT6881
MediaTek chipset MT6980
MediaTek chipset MT8668
MediaTek chipset MT6897
MediaTek chipset MT6988
MediaTek chipset MT8883
MediaTek chipset MT6880
MediaTek chipset MT6815
MediaTek chipset MT6890
MediaTek chipset MT6858
MediaTek chipset MT8873
MediaTek chipset MT6983
MediaTek chipset MT2735
MediaTek chipset MT8678
MediaTek chipset MT8798
MediaTek chipset MT6989
MediaTek chipset MT6833
MediaTek chipset MT6875
MediaTek chipset MT6889
MediaTek chipset MT6886
MediaTek chipset MT6899
MediaTek chipset MT8863
MediaTek chipset MT8771
MediaTek chipset MT8797
MediaTek chipset MT6895
MediaTek chipset MT6990
MediaTek chipset MT8793
MediaTek chipset MT6853

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue sits in MediaTek baseband/modem firmware and is classified as CWE-129 (Improper Validation of Array Index), meaning a value taken from a network-supplied modem message is used to index a structure without a bounds check, producing an out-of-range access that faults and crashes the modem subsystem. Because the trigger arrives over the cellular air interface rather than IP, the CVSS base metric is AV:A (adjacent network) - here the 'adjacency' is RF proximity to a rogue/false base station that the UE has selected and attached to, which is precisely the exploitation condition stated in the advisory and the reason AC is rated High (the attacker must stand up a convincing cell per target and wait for attachment). The vector's PR:N/UI:N confirms no authentication and no user action are needed once attachment has occurred, but the practical barriers - physical/RF proximity, rogue-cell setup effort, and availability-only impact confined to a modem crash - keep this out of remote, internet-reachable territory. Affected CPEs span a wide swath of MediaTek silicon (Dimensity-class smartphone SoCs plus IoT/automotive-adjacent parts such as MT2735/MT2737/MT8668/MT8678/MT8775/MT8797), indicating the same modem codebase is shared across product families.

Know when Mt2735 Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mediatek) PRIMARY 5.3 MEDIUM
AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 5.3 MEDIUM

Requires radio-proximity rogue base station and victim UE attachment, so AV:A and AC:H; no auth needed (PR:N); modem crash yields A:H with no C/I impact.

3.1 AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (mediatek).

CVSS VectorVendor: mediatek

Attack Vector
Adjacent
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

3
CVSS changed
Oct 05, 2026 - 11:22 NVD
5.3 (MEDIUM)
CVE Published
Oct 05, 2026 - 02:16 cve.org
MEDIUM 5.3
CVE Published
Oct 05, 2026 - 02:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In Modem, there is a possible system crash due to a missing bounds check. 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: MOLY01864925 / MOLY01210562; Issue ID: MSV-8303.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
High
MediaTek basebands power a large share of global Android smartphones
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy