CVE-2025-20732VulnerabilityPublished 4 Nov 2025Updated 26 Feb 2026

CVE-2025-20732: MediaTek MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 · Stack Overflow

Affects MediaTek MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986Source CVE Database V5

Not known to be exploited · CVSS 4.2 Medium : upgrade to 19.07 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.2Medium

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 19.07

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 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 MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 to 19.07.

Affected software

Product	Affected	Fixed in
MediaTek, Inc. MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986	Affected <19.07 =21.02	Fixed in 19.07

AI-suggested

1. Apply the vendor-provided patch WCNCR00441510 as soon as it becomes available to ensure the vulnerability is remediated at the source. 2. Upgrade affected devices to SDK versions later than 7.6.7.2 and openWRT versions beyond 21.02 where the vulnerability is fixed. 3. Disable or carefully configure the OceReducedNeighborReport feature if it is enabled, as its state influences exploitability. 4. Implement strict access controls to limit System-level privileges only to trusted administrators and processes, reducing the risk of local exploitation. 5. Monitor device logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected crashes or privilege escalations. 6. For organizations deploying MediaTek-based wireless infrastructure, consider network segmentation to isolate vulnerable devices and limit potential lateral movement. 7. Maintain an inventory of devices using affected chipsets to prioritize patching and risk management efforts. 8. Engage with device vendors and firmware providers to ensure timely updates and security advisories are received and acted upon.

Description

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege (when OceReducedNeighborReport is disabled). User interaction is not needed for exploitation. Patch ID: WCNCR00441510; Issue ID: MSV-4139.

Impact

The primary impact of CVE-2025-20732 is local privilege escalation on devices using affected MediaTek chipsets. An attacker with existing System privileges could exploit this vulnerability to gain higher privileges or execute arbitrary code in kernel mode, potentially compromising the confidentiality, integrity, and availability of the device. This could lead to unauthorized access to sensitive data, disruption of wireless network services, or persistent compromise of network infrastructure devices. Since the vulnerability affects widely deployed chipsets in embedded wireless devices and routers, organizations relying on these devices for network connectivity and security could face increased risk of targeted attacks or lateral movement within their networks. The lack of user interaction required for exploitation further increases the threat level in environments where attackers have some foothold. Although no known exploits are currently in the wild, the vulnerability's presence in critical network components makes timely patching essential to prevent future exploitation.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
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)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 00:36 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats