CVE-2025-10184: OnePlus OxygenOS · Missing Authorization
Affects OnePlus OxygenOSSource CVE Database V5
Not known to be exploited · CVSS 8.2 High · fixed in 16.0.0 : patch OnePlus OxygenOS soon.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 4.3% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.0.0, 15.0.0, 14.0.0 +1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade OnePlus OxygenOS to 16.0.0, 15.0.0, 14.0.0 or 13.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OnePlus OxygenOS | Affected
| Fixed in
|
AI-suggested
Specific mitigation steps include: 1) Immediate update of all OnePlus OxygenOS devices to patched versions once available from the vendor, as no patches are currently linked. 2) Until patches are released, organizations should restrict installation of untrusted or third-party applications on corporate OnePlus devices through Mobile Device Management (MDM) solutions to reduce exposure. 3) Disable or limit SMS-based MFA where possible, replacing it with more secure authentication methods such as hardware tokens or authenticator apps. 4) Monitor telephony-related logs and network traffic for unusual access patterns or data exfiltration attempts. 5) Implement application whitelisting and runtime application self-protection (RASP) to detect and prevent unauthorized access to sensitive content providers. 6) Educate users about the risks of installing unknown apps and encourage prompt reporting of suspicious device behavior. 7) For organizations managing their own device fleets, consider temporarily restricting the use of vulnerable OxygenOS versions until patches are deployed.
Description
The vulnerability allows any application installed on the device to read SMS/MMS data and metadata from the system-provided Telephony provider without permission, user interaction, or consent. The user is also not notified that SMS data is being accessed. This could lead to sensitive information disclosure and could effectively break the security provided by SMS-based Multi-Factor Authentication (MFA) checks. The root cause is a combination of missing permissions for write operations in several content providers (com.android.providers.telephony.PushMessageProvider, com.android.providers.telephony.PushShopProvider, com.android.providers.telephony.ServiceNumberProvider), and a blind SQL injection in the update method of those providers.