# CVE-2026-0127: Memory corruption in Android

> A memory corruption flaw in Android's NRMM decoder allows remote attackers to cause a denial of service via a communication processor crash.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 16 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** A-463414629, GHSA-5vr3-4hgc-ggv8, PUB-A-463414629

## What is CVE-2026-0127?

CVE-2026-0127 is a medium-severity memory corruption vulnerability in Google Android, published on 16 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In NrmmMsgCodec::DecodeUPUTransparentContext of cn_NrmmDecoder.cpp, there is a possible out-of-bounds read due to memory corruption. This could lead to remote denial of service causing a communication processor crash with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Google Android.

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

Apply the vendor's patch.

## Is CVE-2026-0127 being exploited?

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

## 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-0127 and fix it if it is affected.

What it is: CVE-2026-0127 is a medium-severity memory corruption vulnerability in Google Android, published on 16 Jun 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-0127 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-0127/ (Markdown: https://insights.sbomify.com/CVE-2026-0127/index.md)
```

## Sources

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

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