# CVE-2026-20452: Memory corruption in MediaTek chipset

> A heap buffer overflow in the MediaTek WLAN AP driver allows remote code execution for attackers with user privileges.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-mfvp-3qw7-v5gw

## What is CVE-2026-20452?

CVE-2026-20452 is a high-severity memory corruption vulnerability in MediaTek, Inc. MediaTek chipset, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-20452?

It affects 9 products.


Products: Mediatek Mt6890 Firmware, Mediatek Mt7615 Firmware, Mediatek Mt7915 Firmware, Mediatek Mt7916 Firmware, Mediatek Mt7981 Firmware, Mediatek Mt7986 Firmware, Mediatek Mt7990 Firmware, Mediatek Mt7992 Firmware, Mediatek Mt7993 Firmware.

## How do I fix CVE-2026-20452?

No fix has been published for CVE-2026-20452 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-20452 being exploited?

There is no known exploitation of CVE-2026-20452 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Hunt-Benito/mediatek-wlan-heap-overflow-cve-2026-20452-filogic-router-rce (github_poc): https://github.com/Hunt-Benito/mediatek-wlan-heap-overflow-cve-2026-20452-filogic-router-rce

## Other vulnerabilities in MediaTek, Inc. MediaTek chipset

- [CVE-2026-20494](https://insights.sbomify.com/CVE-2026-20494/): Information disclosure in MediaTek chipset (medium 5.5)
- [CVE-2026-20493](https://insights.sbomify.com/CVE-2026-20493/): Memory corruption in MediaTek chipset (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20452 and fix it if it is affected.

What it is: CVE-2026-20452 is a high-severity memory corruption vulnerability in MediaTek, Inc. MediaTek chipset, published on 1 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20452 in the wild and no public exploit code.

Affected product: MediaTek, Inc. MediaTek chipset. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-20452/ (Markdown: https://insights.sbomify.com/CVE-2026-20452/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-20452
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20452
- OSV: https://osv.dev/vulnerability/CVE-2026-20452

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-20452/
Summaries are generated and may contain mistakes; the official description above is the record.