dbcve.org
AndroidOperating system · Google

CVE-2025-0092

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In handleBondStateChanged of AdapterService.java, there is a possible permission bypass due to misleading or insufficient UI. This could lead to remote (proximal/adjacent) information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Bluetooth permission bypass vulnerability in Android's AdapterService where the handleBondStateChanged function fails to properly display bond state changes to the user. The misleading or insufficient UI allows an attacker within proximal/adjacent range to potentially trigger Bluetooth pairing events without the user being adequately informed, leading to information disclosure.

MitigationApply the Android system security update containing the fix for CVE-2025-0092. Users should be cautious of unexpected Bluetooth pairing prompts and verify their device's Bluetooth pairing status after applying the patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 12.0= 12.1= 13.0= 14.0= 15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android OS version
    Go to Settings > About Phone > Android version. Confirm the exact version number matches 12.0, 12.1, 13.0, 14.0, or 15.0.
    Affected if The device runs Android 12.0, 12.1, 13.0, 14.0, or 15.0 and has not received the security patch for this CVE.
  2. Confirm Bluetooth is enabled
    Check if Bluetooth is turned on in Settings > Bluetooth. Also check the quick settings panel for the Bluetooth icon.
    Affected if Bluetooth is enabled and the device is running an affected Android version.
  3. Review paired Bluetooth devices
    Navigate to Settings > Bluetooth > Paired devices list. Look for any unfamiliar or unexpected device entries that you do not recognize.
    Affected if There are paired devices you did not intentionally pair, especially if you did not see a pairing confirmation prompt.
  4. Inspect Bluetooth pairing logs
    Use the system logcat via ADB: 'adb logcat -d | grep -i bond' or check Settings > System > Developer options > Bluetooth HCI snoop log. Look for bonding events without corresponding user notification entries.
    Affected if Bonding events appear in logs without clear user-facing confirmation UI records.

A device is affected if it runs Android 12.0 through 15.0, has Bluetooth enabled, and either shows unexpected paired devices or has log entries indicating bonding without visible user prompts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android system security update containing the fix for CVE-2025-0092. Users should be cautious of unexpected Bluetooth pairing prompts and verify their device's Bluetooth pairing status after applying the patch.

Recommended fix Moderate confidence

Android 15 or January 2025 Android Security Patch level (and subsequent monthly patches)

  1. 1. Navigate to Settings > System > Software Update on the affected Android device
  2. 2. Check for and install any available system updates
  3. 3. Ensure the device updates to Android 15 or receives the January 2025 Android Security Patch level or later
  4. 4. After update, verify the Bluetooth pairing confirmation dialog clearly displays the correct device name and MAC address before accepting
Caveat Android 15 introduces UI changes and may have app compatibility considerations; ensure critical apps are compatible before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0092 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data