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

> A missing bounds check in MediaTek modem firmware allows remote privilege escalation via a rogue base station, requiring user interaction.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-rq5q-2w74-7p99

## What is CVE-2026-20526?

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

### Official description

In Modem, there is a possible out of bounds write due to a missing bounds check. This could lead to remote escalation of privilege, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: MOLY01898195; Issue ID: MSV-8906.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 55 products.


Products: Mediatek Mt2716 Firmware, Mediatek Mt2735 Firmware, Mediatek Mt2737 Firmware, Mediatek Mt6813 Firmware, Mediatek Mt6815 Firmware, Mediatek Mt6833 Firmware, Mediatek Mt6835 Firmware, Mediatek Mt6853 Firmware, Mediatek Mt6855 Firmware, Mediatek Mt6858 Firmware, Mediatek Mt6873 Firmware, Mediatek Mt6875 Firmware, Mediatek Mt6877 Firmware, Mediatek Mt6878 Firmware, Mediatek Mt6879 Firmware, Mediatek Mt6880 Firmware, Mediatek Mt6881 Firmware, Mediatek Mt6883 Firmware, Mediatek Mt6885 Firmware, Mediatek Mt6886 Firmware and 35 more.

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

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

## Is CVE-2026-20526 being exploited?

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

## Other vulnerabilities in MediaTek, Inc. MediaTek chipset

- [CVE-2026-20519](https://insights.sbomify.com/CVE-2026-20519/): Memory corruption in MediaTek chipset (high 7.5)
- [CVE-2026-20520](https://insights.sbomify.com/CVE-2026-20520/): Memory corruption in MediaTek chipset (high 7.5)
- [CVE-2026-20543](https://insights.sbomify.com/CVE-2026-20543/): Information disclosure in MediaTek chipset (medium 5.5)
- [CVE-2026-20500](https://insights.sbomify.com/CVE-2026-20500/): Denial of service in MediaTek chipset (medium 5.5)
- [CVE-2026-20525](https://insights.sbomify.com/CVE-2026-20525/): Denial of service in MediaTek chipset (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-20526 is a high-severity memory corruption vulnerability in MediaTek, Inc. MediaTek chipset, published on 5 Oct 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-20526 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-20526/ (Markdown: https://insights.sbomify.com/CVE-2026-20526/index.md)
```

## Sources

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

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