Skip to main content
VulnerabilityPublished Updated

CVE-2024-56193: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 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

AI-suggested

To mitigate CVE-2024-56193, European organizations should prioritize the following actions: 1) Ensure all Android devices are updated promptly once official patches become available from device manufacturers or Google. 2) Implement strict application control policies to limit installation of untrusted or unnecessary apps that could exploit local vulnerabilities. 3) Employ mobile device management (MDM) solutions to enforce security configurations, including restricting Bluetooth usage or access to Bluetooth adapter information where feasible. 4) Monitor device behavior for unusual Bluetooth activity or unauthorized access attempts. 5) Educate users about the risks of installing apps from unknown sources and the importance of device security hygiene. 6) For critical environments, consider disabling Bluetooth functionality on devices where it is not required to reduce the attack surface. 7) Collaborate with vendors to obtain timely security updates and verify patch deployment status across the device fleet. These measures go beyond generic advice by focusing on controlling local access, application permissions, and device configurations specific to Bluetooth usage.

Description

There is a possible disclosure of Bluetooth adapter details due to a permissions bypass. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…