CVE-2026-28606
Google · Android
A logic error in the handleBondStateChanged function of Android's AdapterService allows unauthenticated attackers to bypass pairing requirements, leading to remote privilege escalation.
Executive summary
A critical logic flaw in Google Android enables unauthenticated remote attackers to escalate privileges without user interaction, posing a severe risk to device integrity.
Vulnerability
The vulnerability exists in the handleBondStateChanged method within AdapterService.java, where a logic error permits the bypass of Bluetooth pairing protocols. As indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N), this flaw is exploitable by an unauthenticated remote attacker with no user interaction required.
Business impact
The ability for an unauthenticated remote actor to escalate privileges on a mobile device presents a catastrophic risk to organizational data security. Successful exploitation could grant an attacker full control over the device, leading to unauthorized access to sensitive corporate communications, credentials, and internal network resources. Given the CVSS score of 9.8, this vulnerability is categorized as critical, necessitating immediate attention to prevent potential large scale compromise of mobile fleets.
Remediation
Immediate Action: Organizations should monitor the official Google Android Security Bulletin for the release of security patches corresponding to the affected Android versions and deploy updates as soon as they become available.
Proactive Monitoring: Security teams should monitor Bluetooth-related logs and device management consoles for anomalous pairing activities or unexpected connection attempts from unknown sources.
Compensating Controls: Where possible, restrict the use of Bluetooth on managed devices in high-security environments or enforce strict policy configurations that limit device discoverability.
Exploitation status
Public Exploit Available: No (unknown)
Analyst recommendation
This vulnerability represents a significant security risk due to its high CVSS score and the lack of required user interaction for exploitation. Administrators must prioritize the identification of affected devices within their infrastructure and prepare for an immediate rollout of vendor-supplied patches. Until patches are applied, enforcing restrictive mobile device management policies regarding wireless connectivity is strongly advised to mitigate the attack surface.
More Google CVEs all →
History
CVE Brief tracked this CVE 2 days before it had a CVSS score.
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- CVSS score assigned 9.8 (3.1)
- Analyst report written