Skip to main content
VulnerabilityPublished Updated

CVE-2025-26438: Google Android · Elevation of Privilege

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Affected software

ProductAffectedFixed in
Google AndroidAffected
  • =15
  • =14
  • =13
Fixed in–

AI-suggested

Organizations should monitor official Google security advisories for patches addressing CVE-2025-26438 and apply them promptly once available. Until patches are released, practical mitigations include disabling Bluetooth on devices when not in use, especially in high-risk environments, to reduce the attack surface. Network segmentation and the use of mobile device management (MDM) solutions can enforce Bluetooth usage policies and detect anomalous Bluetooth activity. Employing endpoint detection and response (EDR) tools with Bluetooth protocol monitoring capabilities can help identify exploitation attempts. Educating users about the risks of connecting to unknown or untrusted Bluetooth devices can further reduce exposure. For enterprise deployments, consider restricting Bluetooth functionality on managed devices or using VPNs and encryption to protect sensitive communications. Regularly updating device firmware and Android OS versions ensures the latest security improvements are in place. Finally, conducting security assessments focused on Bluetooth interfaces can help identify and remediate related weaknesses.

Description

In smp_process_secure_connection_oob_data of smp_act.cc, there is a possible way to bypass SMP authentication due to Incorrect implementation of a protocol. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…