VulnerabilityPublished 2 Mar 2026Updated 6 Mar 2026

CVE-2024-43766: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.07% 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:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GoogleAndroid	Affected =16 =15 =14	Fixed in–

AI-suggested

Monitor official Google Android security bulletins and update devices promptly once patches for CVE-2024-43766 are released.
Until patches are available, limit BLE usage in sensitive environments or disable BLE on devices where not required.
Employ network segmentation and physical security controls to restrict attacker proximity to BLE-enabled devices.
Use BLE communication protocols that implement additional encryption or application-layer security to protect sensitive data beyond the vulnerable BLE stack.
Conduct regular security assessments of BLE-enabled devices and applications to detect anomalous BLE traffic or unauthorized scanning.
Educate users and administrators about the risks of BLE communication interception and encourage cautious use in public or untrusted areas.
For organizations deploying custom BLE solutions, consider implementing cryptographic protections at the application layer to mitigate risks from underlying BLE vulnerabilities.
Monitor threat intelligence sources for any emerging exploit attempts targeting this vulnerability.

Description

In multiple functions of btm_ble_sec.cc, there is a possible unencrypted communication due to Invalid error handling. This could lead to remote (proximal/adjacent) information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Impact

The primary impact of CVE-2024-43766 is the unauthorized disclosure of sensitive information transmitted over BLE on affected Android devices. This can lead to privacy breaches, leakage of device or user data, and potential reconnaissance by attackers to facilitate further attacks. Since BLE is widely used for device pairing, health devices, wearables, and IoT communications, the vulnerability could expose sensitive personal or organizational data. The lack of encryption undermines confidentiality but does not affect data integrity or availability. Organizations with Android device fleets, especially those using BLE for critical communications or in sensitive environments, face risks of data leakage to nearby attackers. This could impact sectors such as healthcare, finance, enterprise mobility, and government, where BLE-enabled devices are prevalent. The proximity requirement limits remote exploitation but does not eliminate risk in public or semi-public spaces. The absence of required privileges or user interaction increases the likelihood of opportunistic attacks. Overall, the vulnerability could erode trust in BLE communications on Android until properly mitigated.

Summary

CVE-2024-43766 is a medium-severity vulnerability identified in Google Android's Bluetooth Low Energy (BLE) security implementation, specifically within multiple functions of the btm_ble_sec.cc source file. The root cause is invalid error handling that leads to certain BLE communications being transmitted without encryption. This flaw violates secure communication principles by allowing sensitive data to be sent in cleartext over BLE channels. Since BLE is a wireless protocol designed for short-range communication, an attacker in close physical proximity can exploit this vulnerability to intercept information that should otherwise be protected. The vulnerability does not require any privileges or user interaction, increasing its risk profile. Affected Android versions include 14, 15, and 16, which cover a significant portion of current Android devices. The vulnerability corresponds to CWE-319, which relates to cleartext transmission of sensitive information. Although no known exploits have been reported in the wild, the lack of encryption in BLE communications can expose confidential data such as device identifiers, pairing information, or other sensitive BLE payloads. The CVSS v3.1 base score is 6.5, reflecting a medium severity with high confidentiality impact but no integrity or availability impact. No patches have been linked yet, so mitigation currently relies on defensive measures and monitoring.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

source.android.com/docs/security/bulletin/2026/2026-03-01 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 17:02 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats