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

> A heap buffer overflow in MediaTek modem firmware allows remote attackers to cause a system crash via a rogue base station.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** Yes
- **Published:** 4 May 2026
- **Updated:** 4 May 2026
- **Also known as:** A-488935936, ASB-A-488935936, GHSA-hjqf-j9p4-gv29, M-MOLY01760138

## What is CVE-2026-20449?

CVE-2026-20449 is a medium-severity memory corruption vulnerability in MediaTek, Inc. MediaTek chipset, published on 4 May 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 system crash due to a heap buffer overflow. This could lead to remote denial of service, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01760138; Issue ID: MSV-6148.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 68 products.


Products: Mediatek Mt2735 Firmware, Mediatek Mt2737 Firmware, Mediatek Mt6739 Firmware, Mediatek Mt6761 Firmware, Mediatek Mt6762 Firmware, Mediatek Mt6763 Firmware, Mediatek Mt6765 Firmware, Mediatek Mt6767 Firmware, Mediatek Mt6768 Firmware, Mediatek Mt6769 Firmware, Mediatek Mt6771 Firmware, Mediatek Mt6779 Firmware, Mediatek Mt6781 Firmware, Mediatek Mt6783 Firmware, Mediatek Mt6785 Firmware, Mediatek Mt6789 Firmware, Mediatek Mt6813 Firmware, Mediatek Mt6815 Firmware, Mediatek Mt6833 Firmware, Mediatek Mt6835 Firmware and 48 more.

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

Apply the vendor's patch.

## Is CVE-2026-20449 being exploited?

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

## Other vulnerabilities in MediaTek, Inc. MediaTek chipset

- [CVE-2026-20433](https://insights.sbomify.com/CVE-2026-20433/): Memory corruption in MediaTek chipset (high 8.8)
- [CVE-2026-20432](https://insights.sbomify.com/CVE-2026-20432/): Memory corruption in MediaTek chipset (high 8.0)
- [CVE-2026-20479](https://insights.sbomify.com/CVE-2026-20479/): Denial of service in MediaTek chipset (high 7.5)
- [CVE-2026-20528](https://insights.sbomify.com/CVE-2026-20528/): Memory corruption in MediaTek chipset (medium 6.7)
- [CVE-2026-20450](https://insights.sbomify.com/CVE-2026-20450/): Denial of service in MediaTek chipset (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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