Learn/bluetoothesp32advisory

ESP32 Bluetooth Advisories in 2026: A Home Device Check

Espressif's 2026 ESP32 Bluetooth advisories, read for a home device: which builds they reach, which tagged release carries each fix, and why Bluetooth goes off after setup.

Signed by M·
Brick porch at dusk where a small green board by the front door holds the bright orb, one golden thread through the window to a dimmer orb on a desktop computer inside
Do the 2026 ESP32 Bluetooth advisories affect my home device?

Only if your firmware was built with an affected ESP-IDF version and the Bluetooth feature the advisory names. Check the ESP-IDF version and sdkconfig of the build, compare them with each Espressif advisory, rebuild on a patched release where one exists, and turn Bluetooth off after provisioning if the device does not need it.

On September 3, 2026, Espressif published two ESP32 Bluetooth advisories for ESP-IDF's Bluedroid host stack. The first, GHSA-v335-fxwc-rc44, is an out-of-bounds read in L2CAP configuration handling that a nearby device can reach without pairing when Classic Bluetooth is on. The second, GHSA-xcpr-5mqp-9qvv, is a read past a media packet in the A2DP sink, reachable by a paired audio source. Earlier in the year Espressif published three advisories in BLE Wi-Fi provisioning. This page is the house reading of all five for a device in your home.

One date mattered when this page went up. The L2CAP advisory lists ESP-IDF 6.1.1 as the fix for the 6.1 line, marked "yet-to-release." On November 12, 2026, the ESP-IDF tags still ended at v6.1 for that line. Updated November 16, 2026: Espressif tagged ESP-IDF v6.1.1 on November 13 and published the release on November 16. The advisory page still reads "yet-to-release" for that row. If your board runs a 6.1 build with Classic Bluetooth, v6.1.1 is now the tag to move to.

Nothing on this page was re-run on a board. It reads Espressif's advisories and documentation and turns them into a check you can do on your own builds. Espressif keeps the full list on its vulnerabilities page.

Which ESP32 Bluetooth advisories reach a home device?

Each ESP32 Bluetooth advisory names a component and a condition. A home device is affected only when its firmware was built with an affected ESP-IDF version and has that component switched on.

The two September advisories need Bluedroid with Classic Bluetooth, also called BR/EDR. The L2CAP one needs a device in radio range. The A2DP one needs a paired audio source. A camera or sensor that never plays audio over Bluetooth usually has no reason to carry Classic Bluetooth, and Espressif's workaround in both advisories is the same: disable Classic Bluetooth or Bluedroid if the product does not need it.

The provisioning advisories are about the moment you hand a device its Wi-Fi password. GHSA-9r76-858f-v6jh (CVE-2026-45542, May 2026) is a heap overflow in protocomm Security 2 over the NimBLE transport, reachable before any credential check. GHSA-h7r3-gmg9-xjmg (CVE-2026-25507, February 2026) is a use-after-free when provisioning stops with Bluetooth deliberately kept on. Both need the device to be provisioning, or to have left its provisioning service running.

How to run an ESP32 Bluetooth advisory check on your own build

You need the project the firmware was built from. A binary on its own does not tell you its configuration.

Read the ESP-IDF version of the build

Find the ESP-IDF checkout or tag the project builds against. In firmware, esp_get_idf_version() from Espressif's system API returns that string, so a device can report it in a status page or log line. Write the version down next to the board name. That one line is most of an ESP32 Bluetooth advisory check.

Check which Bluetooth features the sdkconfig turns on

Open the project's sdkconfig and look for three things: whether CONFIG_BT_ENABLED is set at all, which host stack is chosen, Bluedroid or NimBLE, and whether CONFIG_BT_CLASSIC_ENABLED is set under the Bluedroid options. The Kconfig reference lists them. If Bluetooth is off in the build, these ESP32 Bluetooth advisories do not apply to that firmware. If only Bluetooth Low Energy is on, the Classic advisories do not apply, and the provisioning ones depend on which provisioning code you use.

Match each build to the patched versions

Compare your version with the affected and patched rows in each advisory. Some fixes shipped in tagged releases, such as v6.0.2 and v5.5.5 for L2CAP. Others still read "yet-to-release" on the advisory page even after a tag exists: v6.1.1 was tagged on November 13, 2026, while 5.4.5 was still untagged on November 16. Rebuild on a patched tag where it exists, reflash with espino, and record the new version. If you cannot move a 6.1 build to v6.1.1 yet, turning off Classic Bluetooth is the documented workaround.

Why Bluetooth goes off after setup on a home ESP32 device

Most of these ESP32 Bluetooth advisories need Bluetooth to be listening. The simplest mitigation is a device that stops listening once its job is done.

Provision over Bluetooth, then boot without it

The house provisioning path in rusty_esp_signal already works this way. A browser using Web Bluetooth writes the Wi-Fi credentials, and on the verified ESP32-CAM run the next boot joined Wi-Fi alone in 9.5 seconds with Bluetooth off. That run is the one silicon row on that page. The comparison with Arduino radio sketches keeps every other radio marked as host-verified, not tested on hardware.

Release the controller when Bluetooth is not needed

On ESP-IDF, the Bluetooth controller API documents esp_bt_controller_disable() and esp_bt_controller_deinit(), and esp_bt_mem_release() for a boot that will never use Bluetooth. Those calls are how firmware turns the radio off for the rest of a boot. Avoid keeping the provisioning service alive after setup: that is the condition in the February use-after-free.

Track A, Track B and what this page does not claim

Track A builds on ESP-IDF, so these advisories are the right list to check. Track B is no_std on esp-hal, which does not use ESP-IDF's Bluedroid or protocomm, so these particular entries do not map onto it one to one. The Bluetooth controller underneath is Espressif's blob on both tracks. This page does not claim which host stack any given Janus build links. The afternoon deploy guide is where provisioning sits in the sequence, and the Connect vision holds the radio links. The crates themselves are published through Remade with Rust, and the home computer that adopts the device is MATA.

FAQ

Quick answers for builders evaluating this technology.

How do I find which ESP-IDF version my ESP32 firmware uses?

Check the project you built it from: the ESP-IDF checkout or tag, or the version the build tool reports. In firmware, esp_get_idf_version() returns the version string. A binary from someone else needs its source or release notes.

Is ESP-IDF v6.1.1 out with the Bluetooth fix?

Yes. Espressif tagged ESP-IDF v6.1.1 on November 13, 2026 and published the release on November 16. It is the version the L2CAP and A2DP advisories name as the fix for the 6.1 line, although both advisory pages still mark it yet-to-release.

Does turning Bluetooth off after provisioning help?

Yes for the provisioning advisories. They are reachable while the device advertises or keeps BLE on after setup. A device that provisions once and then boots with Bluetooth off offers no Bluetooth surface for these advisories.

Are the house Janus devices affected by these ESP32 Bluetooth advisories?

This page does not claim either way. The advisories name ESP-IDF components. Check each Janus build the same way: its ESP-IDF version, its Bluetooth host stack and whether Classic Bluetooth is enabled. Nothing here was re-run on a board.

Do I need Classic Bluetooth on an ESP32 sensor or camera?

Usually not. Classic Bluetooth carries audio profiles such as A2DP. Wi-Fi provisioning uses Bluetooth Low Energy. Espressif's own workaround for the Classic advisories is to disable Classic Bluetooth or Bluedroid when a product does not need it.