dbcve.org
AndroidOperating system · Google

CVE-2025-0093

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 unapproved data access due to a missing permission check. This could lead to remote 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 an Android Bluetooth framework vulnerability in AdapterService.java where the handleBondStateChanged function lacks a proper permission check. The missing validation allows any application to access Bluetooth bonding state information without appropriate authorization, leading to unauthorized information disclosure. User interaction is required, likely involving initiating a Bluetooth pairing operation that the attacker can then observe.

MitigationApply the Android security patch for CVE-2025-0093, which adds the missing permission check in the handleBondStateChanged method of AdapterService.java to enforce proper authorization before allowing access to Bluetooth bonding state data.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 version
    Go to Settings > About Phone > Android version and note the exact version number displayed
    Affected if The version is exactly 12.0, 12.1, 13.0, 14.0, or 15.0
  2. Check security patch level
    Go to Settings > About Phone > Security Patch Level and note the date of the installed security update
    Affected if The security patch level is earlier than the month the CVE-2025-0093 fix was released (contact your device vendor for specific dates)
  3. Confirm Bluetooth is in use
    Check if Bluetooth has been enabled on the device or review Bluetooth pairing history in Settings > Bluetooth > Recently paired devices
    Affected if Bluetooth has been actively used for pairing operations, as user interaction initiating a pairing is required for this vulnerability to be exploitable
  4. Review Bluetooth pairing events
    Check system logs (adb logcat -d | grep -i 'bond') or the Bluetooth pairing history for any unexpected or unauthorized pairing events
    Affected if There are pairing events that occurred without the user's explicit knowledge or consent

You are affected if your device runs Android 12.0, 12.1, 13.0, 14.0, or 15.0 with a security patch level predating the CVE fix and has Bluetooth pairing functionality in use.

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 security patch for CVE-2025-0093, which adds the missing permission check in the handleBondStateChanged method of AdapterService.java to enforce proper authorization before allowing access to Bluetooth bonding state data.

Recommended fix Moderate confidence

Android 15 or later security patch level (March 2025+)

  1. Check your Android device's current Android version in Settings > About Phone > Android version
  2. Verify if your device has received the latest Android security patch level in Settings > About Phone > Security Patch Level
  3. If your device is on Android 12.0, 12.1, 13.0, or 14.0, check for available system updates that include the March 2025 or later security patch
  4. If an update is available, back up important data before applying the update
  5. Apply the system update containing the security fix

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0093 — 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-0093 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