Skip to main content
VulnerabilityPublished

CVE-2025-20686: MediaTek MT6890, MT7915, MT7916, MT7981, MT7986 · Heap Overflow

Affects MediaTek MT6890, MT7915, MT7916, MT7981, MT7986Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 19.07 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 19.07
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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, MT7915, MT7916, MT7981, MT7986 to 19.07.

Affected software

ProductAffectedFixed in
MediaTek, Inc. MT6890, MT7915, MT7916, MT7981, MT7986Affected
  • <19.07
Fixed in
  • 19.07

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Identify and inventory all devices using the affected MediaTek chipsets, including routers, access points, and IoT devices, by leveraging network asset management tools and vendor documentation. 2) Monitor vendor communications closely for official patches or firmware updates addressing CVE-2025-20686 and apply them promptly once available. 3) In the absence of immediate patches, implement network segmentation to isolate vulnerable wireless devices from critical internal systems, reducing potential lateral movement. 4) Employ wireless intrusion detection and prevention systems (WIDS/WIPS) to detect anomalous wireless activity that could indicate exploitation attempts. 5) Restrict physical access and proximity to wireless infrastructure where feasible, and consider deploying directional antennas or reducing wireless signal strength to limit exposure. 7) Conduct regular security assessments and penetration tests focusing on wireless infrastructure to identify and remediate potential exploitation paths. 8) Educate IT and security teams about the specific risks of proximity-based wireless attacks to enhance monitoring and incident response readiness.

Description

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

References

Community reviews

Loading reviews…