# CVE-2026-28659: Missing authorization in Android XR

> Local attackers can access other apps' files and escalate privileges in Android XR due to missing permission checks.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-rmpm-q647-ph72

## What is CVE-2026-28659?

CVE-2026-28659 is a critical missing authorization vulnerability in Google Android XR, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In MicroXR Blobstore, there is a possible way to access other app's files due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Google Android Xr.

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

No fix has been published for CVE-2026-28659 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-28659 being exploited?

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

## Other vulnerabilities in Google Android XR

- [CVE-2026-0072](https://insights.sbomify.com/CVE-2026-0072/): Missing authorization in Android XR (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28659 is a critical missing authorization vulnerability in Google Android XR, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28659 in the wild and no public exploit code.

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

## Sources

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

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