CVE-2025-20693VulnerabilityPublished 8 Jul 2025

CVE-2025-20693: MediaTek MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6985, MT6989, MT6990, MT6991, MT7902, MT7920, MT7921, MT7922, MT7923, MT7925, MT7927, MT7932, MT8196, MT8678, MT8796, MT8893 · Out-of-bounds Read

Affects MediaTek MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6985, MT6989, MT6990, MT6991, MT7902, MT7920, MT7921, MT7922, MT7923, MT7925, MT7927, MT7932, MT8196, MT8678, MT8796, MT8893Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 21.02 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 21.02

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

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jul 2025
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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade MediaTek MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6985, MT6989, MT6990, MT6991, MT7902, MT7920, MT7921, MT7922, MT7923, MT7925, MT7927, MT7932, MT8196, MT8678, MT8796, MT8893 to 21.02.

Affected software

Product	Affected	Fixed in
MediaTek, Inc. MT2737, MT6835, MT6878, MT6886, MT6897, MT6899, MT6985, MT6989, MT6990, MT6991, MT7902, MT7920, MT7921, MT7922, MT7923, MT7925, MT7927, MT7932, MT8196, MT8678, MT8796, MT8893	Affected =14.0 <21.02	Fixed in 21.02

AI-suggested

2) For devices where patches are not yet available, implement network-level controls such as segmenting wireless networks, restricting access to trusted devices, and employing strong wireless encryption and authentication to limit attacker proximity. 3) Monitor wireless network traffic for anomalous behavior indicative of reconnaissance or exploitation attempts targeting WLAN STA drivers. 4) Conduct asset inventories to identify all devices using affected MediaTek chipsets and assess their exposure based on deployment context. 5) Collaborate with vendors and suppliers to verify patch status and request timely updates for embedded systems. 6) Employ endpoint detection and response (EDR) solutions capable of detecting unusual memory access patterns or information leakage attempts on affected devices. 7) Educate IT and security teams about the vulnerability specifics to enhance incident response readiness. 8) For critical infrastructure, consider deploying additional physical security measures to reduce the risk of proximal attackers gaining wireless access. These targeted actions go beyond generic advice by focusing on patch management, network segmentation, device inventory, and monitoring tailored to the unique aspects of this vulnerability.

Description

In wlan STA driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote (proximal/adjacent) information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09812521; Issue ID: MSV-3421.

Impact

For European organizations, the impact of CVE-2025-20693 can be substantial, especially for those relying on devices and embedded systems powered by affected MediaTek chipsets. These chipsets are commonly found in smartphones, IoT devices, routers, and embedded industrial equipment. The vulnerability allows attackers within wireless range (proximal or adjacent) to remotely extract sensitive information from device memory without authentication or user interaction. This can lead to leakage of confidential data such as cryptographic keys, credentials, or proprietary information, undermining data confidentiality. In sectors like finance, healthcare, manufacturing, and critical infrastructure, where secure wireless communications are essential, this vulnerability could facilitate espionage or data breaches. Additionally, the vulnerability could be leveraged as a reconnaissance tool to gather intelligence for further attacks. The broad support across Android and embedded Linux platforms (openWRT, Yocto) increases the attack surface. European organizations with extensive wireless device deployments, including smart city infrastructure, industrial control systems, and consumer electronics, are at risk. The lack of user interaction requirement and no need for elevated privileges lowers the barrier for exploitation, increasing the threat level. However, the absence of known exploits in the wild suggests that immediate widespread attacks may not yet be occurring, but proactive mitigation is critical.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

corp.mediatek.com/product-security-bulletin/July-2025 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 02:55 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats