Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Android LE device pairing user-interaction bypass privilege escalation

IdentifiersCVE-2026-0097CWE-693· Protection Mechanism Failure

CVE-2026-0097 is a critical Android System component vulnerability caused by a logic error in multiple locations involved in Bluetooth Low Energy (LE) device pairing. The flaw allows required user interaction during LE pairing to be bypassed. According to the Android security bulletin and associated CVE record, successful exploitation can result in remote privilege escalation from a proximal or adjacent attacker position, without requiring additional execution privileges and without user interaction.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A nearby attacker within Bluetooth adjacency/proximity can bypass the normal user-interaction requirement for LE device pairing and obtain escalation of privilege on the target Android device. The published CVSS vector (AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates potential high impact to confidentiality, integrity, and availability following successful exploitation.

Mitigation

If you can’t patch tonight, do this now.

Until patches are deployed, reduce Bluetooth attack surface by disabling Bluetooth when not needed, avoiding LE pairing in untrusted environments, restricting physical proximity to the device, and enforcing timely OEM security updates. Enterprise defenders can also limit exposure through device management policies that control Bluetooth usage where operationally feasible.

Remediation

Patch, then assume compromise.

Apply the Android June 2026 security updates that include the fix for CVE-2026-0097. Google states that devices with security patch level 2026-06-01 or later address the issues in that patch set, and patch level 2026-06-05 or later addresses all issues from the June 2026 bulletin. Use vendor/OEM-provided updates incorporating the Android System component fix referenced in the Android Security Bulletin.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.