Skip to main content
VulnerabilityPublished

CVE-2025-20684: MediaTek MT7615, MT7622, MT7663 · Out-of-bounds Write

Affects MediaTek MT7615, MT7622, MT7663Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/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

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Inventory and identify all network devices and IoT equipment using MediaTek MT7615, MT7622, or MT7663 chipsets, particularly those running SDK release 5.1.0.0 or earlier. 2) Engage with device vendors and MediaTek to obtain and apply official patches or firmware updates addressing CVE-2025-20684 as soon as they become available. 3) Implement strict access controls to limit user-level access to network devices, reducing the attack surface for local privilege escalation. 4) Monitor network devices for unusual behavior or signs of exploitation, including unexpected privilege escalations or memory corruption symptoms. 5) Employ network segmentation to isolate critical infrastructure and sensitive systems from devices potentially vulnerable to this flaw. 6) Where patching is delayed, consider temporary mitigations such as disabling or restricting wireless AP functionalities on affected devices if feasible. 7) Maintain up-to-date asset management and vulnerability scanning to detect unpatched devices. 8) Educate IT and security teams about the vulnerability to ensure rapid response and remediation.

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: WCNCR00416939; Issue ID: MSV-3422.

References

Community reviews

Loading reviews…