dbcve.org
BtstackApplication · Bluekitchen Gmbh

CVE-2026-28527

HIGH · 7.3 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to 1.8.1 or later.
See remediation →
76/100
Remediation priority · High
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
BlueKitchen BTstack versions prior to 1.8.1 contain an out-of-bounds read vulnerability in the AVRCP Controller GET_PLAYER_APPLICATION_SETTING_ATTRIBUTE_TEXT and GET_PLAYER_APPLICATION_SETTING_VALUE_TEXT handlers that allows nearby attackers to read beyond packet boundaries. Attackers can establish a paired Bluetooth Classic connection and send specially crafted VENDOR_DEPENDENT responses to trigger out-of-bounds reads, causing information disclosure and potential crashes on affected devices.

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 · high confidence

BlueKitchen BTstack versions prior to 1.8.1 contain an out-of-bounds read vulnerability in the AVRCP Controller's GET_PLAYER_APPLICATION_SETTING_ATTRIBUTE_TEXT and GET_PLAYER_APPLICATION_SETTING_VALUE_TEXT handlers. These handlers fail to properly validate packet bounds when processing VENDOR_DEPENDENT responses, allowing an attacker with an established paired Bluetooth Classic connection to read beyond packet boundaries, causing information disclosure and potential crashes.

MitigationUpgrade BlueKitchen BTstack to version 1.8.1 or later which contains the fix for this out-of-bounds read vulnerability in the AVRCP handlers.

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
BtstackApplication
Affected:< 1.8.1

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 BlueKitchen BTstack installation
    Locate the BTstack library files or check your project dependencies for BlueKitchen BTstack (typically libbtstack or btstack source files)
    Affected if BTstack library or source code is present in your environment
  2. Determine installed BTstack version
    Check the BTstack version in your build files, package manager, or the version.h/VERSION file within the BTstack source code
    Affected if The version is less than 1.8.1 (e.g., 1.8.0, 1.7.x, or any version before 1.8.1)
  3. Verify AVRCP Controller is enabled
    Check your BTstack configuration (btstack_config.h or similar) for the define BTSTACK_AVRCP_CONTROLLER or AVRCP controller initialization code
    Affected if AVRCP Controller support is enabled in your build configuration
  4. Confirm VENDOR_DEPENDENT response handling is active
    Review your application code or BTstack configuration to confirm the system processes AVRCP VENDOR_DEPENDENT packets for player application setting attribute/value text queries
    Affected if Your application uses AVRCP Controller functionality that retrieves player application setting attribute or value text from remote devices

You are affected if BlueKitchen BTstack version is below 1.8.1 AND the AVRCP Controller feature with VENDOR_DEPENDENT response handling is enabled in your environment.

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
Upgrade available Upgrade to 1.8.1 or later
Fixed in 1.8.1
Interim mitigation

Upgrade BlueKitchen BTstack to version 1.8.1 or later which contains the fix for this out-of-bounds read vulnerability in the AVRCP handlers.

Recommended fix High confidence

BTstack 1.8.1

  1. Identify all deployments of BTstack in your product or system
  2. Locate the BTstack library or dependency in your build system or package manager
  3. Consult the BTstack release notes or changelog for version 1.8.1 to confirm the security fix is included
  4. Update the BTstack dependency or library to version 1.8.1 or later
  5. Rebuild and recompile your application with the updated BTstack version
  6. Test the updated firmware/application to ensure Bluetooth Classic functionality (especially AVRCP) still operates correctly
  7. Verify the update was successful by checking the BTstack version at runtime if your system supports version reporting
Caveat Review BTstack 1.8.1 release notes for any API changes or behavioral differences in AVRCP or other Bluetooth Classic components that may require application-level code adjustments

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

Fix this in Btstack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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