CVE Intelligence
High

CVE-2026-70387 — OnePlus OxygenOS exposed dangerous method vulnerability

Exposed dangerous method or function and Incorrect Authorization vulnerability in OnePlus OxygenOS on Android. The olc2 logging HAL exposes a binder method that fork()'s and calls execl("/vendor/bin/sh", "sh", "-c", cmd, NULL) with a caller-supplied command string. The only authorization check is getCallingUid() == 0. Because SELinux policy grants binder access to this HAL to a wide client attribute, any uid-0 process in any of those domains (including dumpstate, which is reachable from an unprivileged app via Vulnerability 1) obtains arbitrary command execution. The spawned shell lands in u:r:vendor_qti_init_shell:s0 SELinux context via a policy type_transition, a domain holding all Linux capabilities. This issue affects OxygenOS: from 16.1.0 before 16.1.10.500, from 16.0.0 before 16.0.5.1200, and from 15.0.0 before 15.0.0.2000.

Published Oct 21, 2026 · Updated Oct 22, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: ENISA

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+4
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.31%
ahead of 23% of scored CVEs · Oct 26, 2026
Affects
OnePlus
OxygenOS
CVSS base
8.4
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (OnePlus OxygenOS).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
OnePlus OxygenOS ≥ 16.0.0 and < 16.0.5.1200≥ 15.0.0 and < 15.0.0.2000 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Attack requirements
None
Privileges required
High
User interaction
None
Scope
X
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
High
Availability (vulnerable system)
High
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.4 CVSS 4.0 High — — a6d3dc9e-0591-4a13-bce7-0f5b31ff6158 via NIST National Vulnerability Database
8.4 CVSS 4.0 High — — ENISA via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: a6d3dc9e-0591-4a13-bce7-0f5b31ff6158)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-749

Other CVEs with this weakness →

EPSS over time FIRST

Oct 21, 2026 → Oct 26, 2026 · 6 reading(s) · max 0.31%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 22, 2026 · NIST National Vulnerability Database
  • Affected products removed · 1
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · oneplus/oxygenos
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 21, 2026
  • CVSS changed · 8.4
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • CVE published
    Oct 21, 2026 · ENISA

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 21, 2026 – Oct 22, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

4 on the record

Elsewhere on this site

OnePlus
every CVE for this vendor
CWE-749
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-70386 OnePlus OxygenOS improper neutralization of special elements vulnerability 5d
  • CVE-2025-10184 OnePlus OxygenOS Telephony provider permission bypass Sep 23, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-70387 is "OnePlus OxygenOS exposed dangerous method vulnerability", rated High. It affects OxygenOS (OnePlus); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. EPSS 0.31% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.