# CVE-2026-92173: Privilege escalation in Meta Horizon OS

> An attacker can exploit a flaw in MediaSyncJobReceiver to impersonate privileged system packages, enabling privilege escalation and security bypasses.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-x7qm-j22r-cgcw

## What is CVE-2026-92173?

CVE-2026-92173 is a critical vulnerability in Meta Horizon OS, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Prior to v74.0.0.878.1682 of Meta Horizon OS, MediaSyncJobReceiver could be induced to send a privileged PendingIntent including a com.oculus.vrshell CallerIdentity to an arbitrary application listening via NotificationListenerService. That would allow the application to impersonate the com.oculus.vrshell package, as well as packages signed with the same key, towards any endpoint within the OS that uses CallerIdentity authentication.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

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


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

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

## Is CVE-2026-92173 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92173 is a critical vulnerability in Meta Horizon OS, published on 30 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-92173 in the wild and no public exploit code.

Affected product: Meta Horizon OS. 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-92173/ (Markdown: https://insights.sbomify.com/CVE-2026-92173/index.md)
```

## Sources

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

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