CVE-2025-20682: MediaTek MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986 · Out-of-bounds Write
Affects MediaTek MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 19.07 as a priority.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 19.07
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation 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 26 Oct 2026.
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
| Fixed in
|
AI-suggested
To mitigate this vulnerability effectively, European organizations should: 1) Identify all devices using the affected MediaTek chipsets and verify firmware versions against the vulnerable SDK and openWRT releases. 3) Where immediate patching is not possible, implement strict access controls to limit local user privileges on affected devices, minimizing the risk of exploitation. 4) Employ network segmentation to isolate vulnerable devices from critical infrastructure and sensitive data repositories. 5) Use host-based intrusion detection systems (HIDS) and endpoint protection solutions capable of detecting anomalous behavior indicative of privilege escalation attempts. 6) Regularly audit device configurations and user accounts to ensure no unauthorized local access exists. 8) Educate IT staff and users about the risks of local privilege escalation vulnerabilities and enforce strong physical and logical security controls to prevent unauthorized device access.
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 with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00416937; Issue ID: MSV-3445.