Skip to main content
VulnerabilityPublished Updated

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

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:42 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 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

  1. Immediately enforce strict Bluetooth device pairing policies, limiting pairing to trusted devices only and regularly auditing paired device lists.
  2. Disable Bluetooth functionality on devices where it is not essential, especially in high-security environments.
  3. Monitor Bluetooth traffic for unusual activity that could indicate exploitation attempts.
  4. Deploy network segmentation and endpoint detection solutions that can identify anomalous Bluetooth-related behaviors.
  5. Once Google releases official patches for affected Android versions, prioritize their deployment across all devices.
  6. Educate users and administrators about the risks associated with Bluetooth connections and encourage vigilance regarding unknown or unexpected pairing requests.
  7. Consider using mobile device management (MDM) solutions to enforce security policies and remotely manage Bluetooth settings.
  8. Stay updated with threat intelligence feeds for any emerging exploit reports related to this vulnerability.

Description

In avdt_msg_ind of avdt_msg.cc, there is a possible memory corruption due to type confusion. This could lead to paired device escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…