Skip to main content
Menu
CVEs

CVE

Espressif ESP-IDF remote crash via overflow in BLE Mesh GATT read handler

Only affects ESP-IDF builds using the Bluedroid host with BLE Mesh GATT bearers (PB-GATT or GATT Proxy) enabled. Fixed in 5.2.8, 5.3.6, 5.5.6 and 6.0.3.

CVE-2026-113781EUVD-2026-127194

Written by a model from the sources below. Verify against them.

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

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 5.2.8, 5.3.6, 5.5.6, 6.0.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.2.8, 5.3.6, 5.5.6, 6.0.3.

Published
Last modified
Reference
Last checked
7/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

A buffer overflow in ESP-IDF's BLE Mesh GATT server lets an attacker within Bluetooth LE range, without logging in or any user action, crash the device and force it to restart, and it may also corrupt further memory. The attacker connects to an exposed PB-GATT provisioning or Mesh Proxy service and sends a crafted read request that triggers the flaw.

Original description

ESP-IDF is the Espressif Internet of Things (IoT) Development Framework. Prior to 5.2.8, 5.3.6, 5.5.6, and 6.0.3, the Bluedroid BLE Mesh GATT server read handler bt_mesh_bta_gatts_cb in esp_ble_mesh stores a signed attribute-read callback length in an unsigned 16-bit variable. A negative ATT error code is therefore interpreted as a very large successful length and used for a memory copy from a small stack buffer into the GATT response structure. A remote attacker within Bluetooth LE range who can connect to an exposed PB-GATT provisioning or Mesh Proxy service can trigger a failed attribute read with a crafted request. On devices where the affected attributes are accessible without pairing, exploitation requires neither pairing nor user interaction; access requirements depend on device configuration. The resulting out-of-bounds read and stack-based buffer overflow corrupts the Bluetooth host task stack, causing a crash and device restart and potentially further memory corruption. The issue affects devices built with CONFIG_BT_BLUEDROID_ENABLED=y and BLE Mesh GATT enabled; the NimBLE host path is not affected. This issue is fixed in versions 5.2.8, 5.3.6, 5.5.6, and 6.0.3.

Who should check

Teams shipping ESP-IDF firmware with the Bluedroid host and BLE Mesh GATT (PB-GATT or Mesh Proxy) enabled, on releases v5.2 through v6.0.2

“Affected supported releases are v5.2 through v5.2.7, v5.3 through v5.3.5, v5.4 through v5.4.4, v5.5 through v5.5.5, and v6.0 through v6.0.2.”

github.com

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Unknown. Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 5.2.8, 5.3.6, 5.5.6, 6.0.3.

  • Workaround: Disable the BLE Mesh GATT bearers (PB-GATT and GATT Proxy) when not required, or build with the NimBLE host

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-113781 (ESP-IDF: Buffer Overflow in BLE Mesh GATTS Read Callback Handler), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-113781 (entry last updated 2026-11-17):
Affected:
- espressif esp-idf: through 5.1.7; from 5.2.0, fixed in 5.2.8; from 5.3.0, fixed in 5.3.6; from 5.4.0, through 5.4.4; from 5.5.0, fixed in 5.5.6; from 6.0.0, fixed in 6.0.3
Fixed versions: 5.2.8, 5.3.6, 5.5.6, 6.0.3.
Conditions (all must be true for the bug to be hit):
- Device built with the Bluedroid host and BLE Mesh enabled (source: https://github.com/espressif/esp-idf/security/advisories/GHSA-rjvf-fxv5-x87j)
- A BLE Mesh GATT bearer (PB-GATT or GATT Proxy) is enabled and advertising (source: https://github.com/espressif/esp-idf/security/advisories/GHSA-rjvf-fxv5-x87j)
- Affected ESP-IDF release lines only (v5.2 to v5.2.7, v5.3 to v5.3.5, v5.4 to v5.4.4, v5.5 to v5.5.5, v6.0 to v6.0.2) (source: https://github.com/espressif/esp-idf/security/advisories/GHSA-rjvf-fxv5-x87j)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
Workaround: Disable the BLE Mesh GATT bearers (PB-GATT and GATT Proxy) when not required, or build with the NimBLE host (source: https://github.com/espressif/esp-idf/security/advisories/GHSA-rjvf-fxv5-x87j)
CISA KEV: CVE-2026-113781 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-113781 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/espressif/esp-idf/security/advisories/GHSA-rjvf-fxv5-x87j
- https://github.com/espressif/esp-idf/commit/00adfb3cbcf9a4a9e6ff1a2b99937a253887f8ca
- https://github.com/espressif/esp-idf/commit/2fed52c72944781562fb63b8be7b6d29f3cff97e
- https://github.com/espressif/esp-idf/commit/812f7de59efdf79529e1c10cd788d324fa05f10d
- https://github.com/espressif/esp-idf/commit/c146056e55815cad542aff640a21e3f94879dd6a
- https://github.com/espressif/esp-idf/commit/ce902a85135b0e069c125b11735aa8757fb528b2
- https://github.com/espressif/esp-idf/commit/f9da09de61e98c9074d5cb89d5b1b4c37739fa85
- https://github.com/espressif/esp-idf/releases/tag/v5.2.8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-113781
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-113781"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • espressif esp-idf

    through 5.1.7; From 5.2.0 · fixed in 5.2.8; From 5.3.0 · fixed in 5.3.6; From 5.4.0 · through 5.4.4; From 5.5.0 · fixed in 5.5.6; From 6.0.0 · fixed in 6.0.3

Evidence 13

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 10

  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository
  6. Repository
  7. Repository
  8. Repository
  9. Repository
  10. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-113781

Is CVE-2026-113781 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A buffer overflow in the BLE Mesh GATT read callback handler causes an out-of-bounds read and a stack buffer overflow that corrupts the Bluetooth host task stack. This can crash the device and restart it, and may lead to further memory corruption.Source: github.com

Which versions are affected by CVE-2026-113781?

esp-idf: through 5.1.7; from 5.2.0 before 5.2.8; from 5.3.0 before 5.3.6; from 5.4.0 through 5.4.4; from 5.5.0 before 5.5.6; from 6.0.0 before 6.0.3.Source: cve.now feed data

Am I affected, and how do I check?

ESP-IDF v5.2 through v5.2.7, v5.3 through v5.3.5, v5.4 through v5.4.4, v5.5 through v5.5.5, and v6.0 through v6.0.2 are listed as affected. The bug needs the Bluedroid host (CONFIG_BT_BLUEDROID_ENABLED=y), BLE Mesh enabled, and a BLE Mesh GATT bearer (PB-GATT or GATT Proxy) enabled and advertising, so check the ESP-IDF version and these settings in the project configuration.Source: github.com

How do I fix CVE-2026-113781?

Upgrade to ESP-IDF 5.2.8, 5.3.6, 5.5.6, or 6.0.3, matching your release line. No fixed version is listed for the 5.4 line. As an interim mitigation, disable the BLE Mesh GATT bearers (PB-GATT and GATT Proxy) when they are not required, or build with the NimBLE host, which the advisory says is not affected.Source: github.com

More CVEs