MediaTek chipset: Heap-based Buffer Overflow
CVE-2026-20452 is a high-severity heap-based buffer overflow vulnerability in MediaTek chipset from MediaTek, with a CVSS 3.1 base score of 8.0 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. Affected MediaTek chipset versions: MT6890; MT7615; MT7915, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.43% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of MediaTek chipset you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on corp.mediatek.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MediaTek | MediaTek chipset | MT6890; MT7615; MT7915; MT7916; MT7981; MT7986; MT7990; MT7992; and 1 more ranges | Not stated |
| MediaTek | Mt6890 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7615 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7915 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7916 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7981 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7986 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7990 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7992 Firmware | Not specified in the record | Not stated |
| MediaTek | Mt7993 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
In wlan AP driver, there is a possible memory corruption due to a heap buffer overflow. This could lead to remote (proximal/adjacent) code execution with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00480138; Issue ID: MSV-6295.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- 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 checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in MediaTek chipset
- 8.4 High severity
- 7.5 High severity
- 8.4 High severity
Recent Heap-based Buffer Overflow vulnerabilities
- 7.8 High severity
- 8.0 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.