MediaTek WLAN Driver
CVE-2025-20710
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition within Wi-Fi range of AP
-
DeliverySend crafted wireless frames
-
ExploitTrigger integer overflow in AP driver
-
ExecutionCause out-of-bounds write
-
ImpactEscalate privileges in driver context
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must be within wireless (adjacent/proximal) range of a device running the vulnerable MediaTek WLAN AP driver - consistent with CVSS AV:A - so this is not internet-wide remotely exploitable; physical radio proximity is the primary limiting factor. Within that range, no authentication (PR:N) and no user interaction (UI:N) are required, so default-configured access points operating as an AP with the affected MediaTek WLAN driver are exploitable by crafted wireless traffic that triggers the integer overflow. The flaw is specific to the AP (access-point) driver path, so devices deployed purely as Wi-Fi clients/stations may not expose the vulnerable code path. |
| Impact | Signals are moderate-to-serious but not critical in practice. The CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N, C:H/I:H/A:H = 8.8) indicates an adjacent-network, low-complexity, unauthenticated flaw requiring no user interaction and yielding full compromise of the affected component - a genuinely dangerous profile for anything in Wi-Fi radio range. The key limiter is AV:A (adjacent), not AV:N: the attacker must be within wireless proximity of the AP, which sharply narrows mass/remote exploitation versus an internet-facing bug. Exploitation-probability signals are low and consistent with each other: EPSS is 0.30% (20th percentile), there is no CISA KEV listing, and no public exploit code is referenced - i.e., no public exploit identified at time of analysis. No SSVC decision data was provided in the input, so automatable/exploitation/technical-impact cannot be evaluated against that framework. Net: this is a technically high-impact memory-corruption EoP (integer overflow → OOB write, CWE-190) that merits patching on affected MediaTek Wi-Fi AP deployments, but current real-world exploitation risk is low and physically gated by adjacency rather than widespread remote mass-exploitation. No conflicting signals were found between the description and the CVSS vector; both agree on adjacent, no-auth, no-UI exploitation. |
| Exploit ScenarioDerived | An attacker within Wi-Fi radio range of a device running the vulnerable MediaTek WLAN AP driver sends specially crafted wireless frames that trigger an integer overflow in the AP driver, producing an out-of-bounds write. With no authentication and no user interaction required, the memory corruption is leveraged to escalate privileges within the driver/kernel context. No public proof-of-concept or exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Out-of-bounds write in MediaTek's WLAN access-point driver lets an attacker within wireless range corrupt memory and escalate privileges on the affected device, with no authentication or user interaction required (CVSS:3.1/AV:A/AC:L/PR:N/UI:N, score 8.8). An integer overflow in the AP driver code path results in an out-of-bounds write that can yield high confidentiality, integrity, and availability impact on the open-source MediaTek software development kit and on OpenWrt releases 19.07.0 and 21.02.0, which ship the affected driver. Exploitability is bounded by radio proximity - the flaw is not internet-reachable - and there is no public exploit identified at time of analysis, with EPSS at 0.30% (20th percentile), indicating low near-term exploitation likelihood despite the high severity score. MediaTek has issued a fix (Patch ID WCNCR00418785) referenced in its October 2025 product security bulletin.
RemediationAI
Apply the MediaTek driver fix identified by Patch ID WCNCR00418785 as published in the October 2025 MediaTek product security bulletin (https://corp.mediatek.com/product-security-bulletin/October-2025); because the SDK is distributed to OEMs, the practical action is to install the firmware update your router/AP vendor issues for the affected chipset, and to confirm with that vendor that the WCNCR00418785 driver change is included - patch status is 'Patch available per vendor advisory' with no public standalone version number to cite. For OpenWrt, note that 19.07.0 and 21.02.0 are end-of-life branches and will not receive this fix, so migration to a currently supported OpenWrt release (or a vendor firmware based on one) is required, with the trade-off of re-validating custom packages and configuration during the upgrade. Where patching cannot be completed immediately, short-term compensating controls are to reduce the attack surface rather than block a port: disable AP/repeater mode on affected devices so the vulnerable driver path is not exercised (devices used purely as wireless clients/stations generally do not expose the AP code path), or if the unit must remain an AP, physically constrain its coverage area and channel plan to shrink the adjacent-attacker radius - though this only reduces probability and does not eliminate exposure. Filtering or firewalling wireless frames is not a viable mitigation here because the corruption occurs in driver-level processing of over-the-air frames before higher-layer policy is applied, so prioritize obtaining vendor firmware containing WCNCR00418785.
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 vulnerability is classified as CWE-190 (Integer Overflow or Wraparound) and lives in the MediaTek WLAN driver's access-point code path, where an unchecked length or index calculation overflows and produces an out-of-bounds write to adjacent memory (tagged both as Buffer Overflow and Integer Overflow). Because the driver processes frames received over the air, the attack surface is the wireless interface itself, which the CVSS vector reflects with AV:A (adjacent network) rather than AV:N - physical radio proximity is required, but no credentials (PR:N) and no user interaction (UI:N) are needed once in range. The AP-specific path matters: CPE data ties the issue to Mediatek's software development kit and to OpenWrt 19.07.0 and 21.02.0, both of which integrate MediaTek Wi-Fi drivers, so devices configured as access points or repeaters using those drivers expose the vulnerable logic, while devices running purely in station/client mode may not reach the affected code. The MITRE-assigned CWE and MediaTek's own issue tracking (MSV-3515) confirm this is a vendor-acknowledged memory-safety defect rather than a logic or configuration weakness.
Know when Openwrt 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
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AV:A because exploitation requires Wi-Fi radio proximity; AC:L/PR:N/UI:N per crafted frames needing no auth or interaction; C/I/A:H for driver-level privilege escalation via OOB write.
Primary rating from Vendor (mediatek).
CVSS VectorVendor: mediatek
DescriptionCVE.org
In wlan AP driver, there is a possible out of bounds write due to an integer overflow. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00418785; Issue ID: MSV-3515.
Executive ViewAI
MediaTek's WLAN access-point driver, shipped in OpenWrt 19.07.0 and 21.02.0 and the MediaTek SDK, contains an unauthenticated adjacent out-of-bounds write that can let an attacker within wireless range corrupt memory and escalate privileges. This affects organizations using affected OpenWrt or MediaTek-based access points, especially those with wireless coverage extending beyond trusted physical boundaries. No public exploit has been identified and EPSS is low, but the high severity and lack of a confirmed available patch in the provided data warrant prioritized inventory, vendor verification, and network segmentation.
No vendor-released patch identified at time of analysis; if MediaTek Patch ID WCNCR00418785 is confirmed applicable, apply vendor patch, otherwise restrict wireless access to trusted clients, reduce AP radio range, segment WLANs from management and internal networks, disable unused AP services, and monitor for crashes or memory corruption indicators.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
Affected Products (CPE)CVE.org
In wlan service, there is a possible out of bounds write due to improper input validation. Rated critical severity (CVSS
An issue was discovered in OpenWrt 18.06.0 to 18.06.6 and 19.07.0, and LEDE 17.01.0 to 17.01.7. Rated high severity (CVS
An issue was discovered in OpenWrt libuci (aka Library for the Unified Configuration Interface) before 15.05.1 as used o
cgi_handle_request in uhttpd in OpenWrt through 18.06.1 and LEDE through 17.01 has unauthenticated reflected XSS via the
In wlan service, there is a possible out of bounds write due to an incorrect bounds check. Rated critical severity (CVSS
An exploitable information leak vulnerability exists in the ustream-ssl library of OpenWrt, versions 18.06.4 and 15.05.1
An exploitable information leak vulnerability exists in the ustream-ssl library of OpenWrt, versions 18.06.4 and 15.05.1
Remote privilege escalation in Android WLAN AP driver via packet injection.
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
Remote code execution in OpenWrt's mDNS daemon (versions before 24.10.6 and 25.12.1) allows unauthenticated attackers to
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB