dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-20700

HIGH · 8.8 CVSS v3.1 Published 2025-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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 the Airoha Bluetooth audio SDK, there is a possible permission bypass that allows access critical data of RACE protocol through Bluetooth LE GATT service. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not 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

A permission bypass vulnerability in the Airoha Bluetooth audio SDK allows unauthorized access to critical RACE protocol data through the Bluetooth LE GATT service. The RACE protocol lacks proper access control checks, enabling an attacker with Bluetooth LE connectivity to escalate privileges remotely without user interaction.

MitigationApply vendor patches or firmware updates for the Airoha Bluetooth audio SDK that implement proper authentication and authorization checks for RACE protocol access via GATT services. Restrict GATT service permissions to enforce role-based access controls.

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

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Airoha Bluetooth audio SDK usage
    Determine if the target device or software implements the Airoha Bluetooth audio SDK. Review device firmware documentation, SDK references in software manifests, or hardware specifications for Airoha chip/binding.
    Affected if The device firmware or software explicitly uses the Airoha Bluetooth audio SDK.
  2. Verify Bluetooth LE connectivity is enabled
    Check device Bluetooth settings or firmware configuration to confirm Bluetooth LE (BLE) is active. Use Bluetooth scanner tools or review BLE advertising data from the device.
    Affected if Bluetooth LE is enabled and the device is discoverable or connectable over BLE.
  3. Locate RACE protocol GATT service exposure
    Connect to the device via BLE GATT and enumerate services. Look for RACE protocol service UUIDs or proprietary vendor services that handle RACE data. Use BLE client tools (nRF Connect, gatttool) to discover services.
    Affected if The device exposes a GATT service handling RACE protocol data without authentication characteristics.
  4. Test RACE protocol access control
    Attempt to read/write to RACE protocol characteristics without prior authentication or pairing. Observe if read/write operations succeed or return authorization errors.
    Affected if RACE protocol GATT characteristics are accessible without proper authentication or authorization checks.
  5. Compare installed SDK version to vendor advisories
    Extract the firmware version or SDK library version from the device. Check vendor security advisories for CVE-2025-20700 and compare against reported affected version ranges if provided.
    Affected if The installed SDK/firmware version matches the range identified as vulnerable in vendor guidance.

A user is affected if their device runs the Airoha Bluetooth audio SDK with BLE enabled, exposes the RACE protocol via GATT without access controls, and lacks the vendor patch for CVE-2025-20700.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches or firmware updates for the Airoha Bluetooth audio SDK that implement proper authentication and authorization checks for RACE protocol access via GATT services. Restrict GATT service permissions to enforce role-based access controls.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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