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

> A missing bounds check in MediaTek chipset firmware allows local privilege escalation via out-of-bounds write, requiring prior System privilege.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** A-527617087, ASB-A-527617087, GHSA-76m9-f2pj-7mwp, M-ALPS10965550, M-ALPS11393405

## What is CVE-2026-20497?

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

### Official description

In geniezone, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10965550 / ALPS11393405; Issue ID: MSV-6941.

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

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

It affects 11 products.


Products: Mediatek Mt6989 Firmware, Mediatek Mt8755 Firmware, Mediatek Mt8768 Firmware, Mediatek Mt8771 Firmware, Mediatek Mt8775 Firmware, Mediatek Mt8781 Firmware, Mediatek Mt8791t Firmware, Mediatek Mt8792 Firmware, Mediatek Mt8796 Firmware, Mediatek Mt8797 Firmware, Mediatek Mt8798 Firmware.

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

Apply the vendor's patch.

## Is CVE-2026-20497 being exploited?

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

## Other vulnerabilities in MediaTek, Inc. MediaTek chipset

- [CVE-2026-20481](https://insights.sbomify.com/CVE-2026-20481/): Memory corruption in MediaTek chipset (medium 6.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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