Skip to content
major vulnerability· requires attention

Unauthenticated remote privilege escalation in Android's Bluetooth stack; affects ubiquitous Android devices and can lead to wide impact across organizations.

Mobile

CVE-2026-28606

9.8
Critical
EPSS 0.29%Patch availableSep 11, 2026

Android Bluetooth pairing bypass allows remote privilege escalation without user consent.

common questions

Is CVE-2026-28606 being exploited?

Not confirmed. CVE-2026-28606 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-28606?

CVE-2026-28606 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-28606?

Yes. A fix has been recorded for CVE-2026-28606. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-28606 affect?

CVE-2026-28606 affects Android devices, Android Bluetooth stack (AdapterService). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-28606?

Apply Android security updates immediately; disable Bluetooth where possible.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Android devicesAndroid Bluetooth stack (AdapterService)
impact

Remote privilege escalation on Android via Bluetooth pairing bypass; attacker gains elevated privileges without user interaction.

action required

Immediate action required

affected versions
Google Android
  • affected17
  • affected16-qpr2
  • affected16
  • affected15

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free