Prior to v66.0.0.733.524 of Meta Horizon OS, OVRMediaService could be induced to send a privileged PendingIntent including a com.oculus.horizon CallerIdentity to an arbitrary application registering for com.oculus.systemactivities.SCREENSHOT via a broadcast receiver. That would allow the application to impersonate the com.oculus.horizon package towards any endpoint within the OS that uses CallerIdentity authentication.
Severity
CVSS 3.1
8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3%(unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-923Improper Restriction of Communication Channel to Intended Endpoints
Show the promptExplain CVE-2026-92172 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92172?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92172?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92172 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
meta platforms, inc:meta horizon os
Versions
From the CNA's record in the CVE List.
Product
Affected
Meta Platforms, Inc Meta Horizon OS
from v0.0.0.0.0 before v66.0.0.733.524
Attack patterns (CAPEC)
CAPEC-161 Infrastructure Manipulation Severity: High
CAPEC-481 Contradictory Destinations in Traffic Routing Schemes Likelihood: Medium · Severity: High
CAPEC-501 Android Activity Hijack Severity: Medium
CAPEC-697 DHCP Spoofing Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.