# CVE-2026-20467: Privilege escalation in MediaTek chipset

> A missing bounds check in MediaTek apusys allows local privilege escalation for attackers with System privileges.

- **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-518564544, ASB-A-518564544, GHSA-629p-7h2h-8hf5, M-AUTO00837766

## What is CVE-2026-20467?

CVE-2026-20467 is a medium-severity 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 apusys, there is a possible escalation of privilege 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: AUTO00837766; Issue ID: MSV-6767.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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


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

Apply the vendor's patch.

## Is CVE-2026-20467 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-20467 is a medium-severity 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-20467 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-20467/ (Markdown: https://insights.sbomify.com/CVE-2026-20467/index.md)
```

## Sources

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

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