CVE-2026-81507: ESF-IDF: Bluetooth Classic L2CAP Heap Memory Disclosure Allowing Unauthorized Access to Sensitive Data

Published Oct 13, 2026
·
Updated

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. Prior to 5.2.8, 5.3.6, 5.5.5, 6.0.3, and 6.1-rc1, ESP-IDF BlueDroid L2CAP configuration-option processing in l2cmain.c and l2cutils.c does not consistently validate option lengths against the remaining received packet bytes. A remote unauthenticated BR/EDR peer within radio range can send a malformed L2CAP configuration request that causes an out-of-bounds read, and under some runtime conditions limited adjacent Bluetooth stack memory can be included in an outbound L2CAP Configuration Response. The issue affects ESP32-class products using the BlueDroid host stack with Classic Bluetooth enabled. This issue is fixed in 5.2.8, 5.3.6, 5.5.5, 6.0.3, and 6.1-rc1.

Affected Software

1 affected component
Espressif ESP-IDF<5.2.8, <5.3.6, <5.5.5, <6.0.3, <6.1-rc1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Espressif ESP-IDF to a version that resolves this vulnerability.

    Fixed in 5.2.8
  2. Upgrade

    Upgrade Espressif ESP-IDF to a version that resolves this vulnerability.

    Fixed in 5.3.6
  3. Upgrade

    Upgrade Espressif ESP-IDF to a version that resolves this vulnerability.

    Fixed in 5.5.5
  4. Upgrade

    Upgrade Espressif ESP-IDF to a version that resolves this vulnerability.

    Fixed in 6.0.3
  5. Upgrade

    Upgrade Espressif ESP-IDF to a version that resolves this vulnerability.

    Fixed in 6.1-rc1

Event History

Oct 13, 2026
CVE Published
via MITRE·03:12 PM
Data Sourced
via MITRE·03:12 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

ESP32-class products using the ESP-IDF BlueDroid host stack with Classic Bluetooth enabled are affected when running versions earlier than 5.2.8, 5.3.6, 5.5.5, 6.0.3, or 6.1-rc1.

2

What does an attacker need to exploit this issue?

An attacker needs only to be an unauthenticated Bluetooth BR/EDR peer within radio range. They can send a malformed L2CAP configuration request; no user interaction is required.

3

What information could be exposed?

Under some runtime conditions, the device may include limited adjacent Bluetooth stack memory in an outbound L2CAP Configuration Response. The disclosed data may contain sensitive information.

4

What is the available remediation?

Update ESP-IDF to 5.2.8, 5.3.6, 5.5.5, 6.0.3, or 6.1-rc1, as appropriate for the release line in use.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203