# CVE-2026-28609: Memory corruption in Android

> An out-of-bounds write in Android's MatroskaExtractor allows remote code execution without user interaction or additional privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** A-485377744, ASB-A-485377744, GHSA-6cg4-96xx-xg28

## What is CVE-2026-28609?

CVE-2026-28609 is a high-severity memory corruption vulnerability in Google Android, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In read of MatroskaExtractor.cpp, there is a possible out-of-bounds write due to improper casting. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

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

It affects 1 product.


Products: Google Android.

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

Apply the vendor's patch.

## Is CVE-2026-28609 being exploited?

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

Public exploit code:

- Proof-of-concept and instrumented reproduction harness for CVE-2026-28609, an out-of-bounds write in Android's MatroskaExtractor reachable via a crafted WebM file with a big-endian PCM audio track. (github_poc): https://github.com/devrodT2/CVE-2026-28609-matroska-pcm-oob

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28609 is a high-severity memory corruption vulnerability in Google Android, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28609 in the wild and no public exploit code.

Affected product: Google Android. 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-28609/ (Markdown: https://insights.sbomify.com/CVE-2026-28609/index.md)
```

## Sources

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

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