CVE-2026-113781 json
ESP-IDF: Buffer Overflow in BLE Mesh GATTS Read Callback Handler
published 16d ago modified 15h ago also EUVD-2026-127194 , GHSA-rjvf-fxv5-x87j
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository espressif/esp-idf. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/espressif/esp-idf@00adfb3 commit
- github.com/espressif/esp-idf@2fed52c commit
- github.com/espressif/esp-idf@812f7de commit
- github.com/espressif/esp-idf@c146056 commit
- github.com/espressif/esp-idf@ce902a8 commit
- github.com/espressif/esp-idf@f9da09d commit
- github.com/espressif/esp-idf/releases/tag/v5.2.8 release
- github.com/espressif/esp-idf/releases/tag/v5.3.6 release
- github.com/espressif/esp-idf/releases/tag/v5.5.6 release
- github.com/espressif/esp-idf/releases/tag/v6.0.3 release
Is CVE-2026-113781 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16h ago
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
Affected products
- espressif esp-idf
Classification
References
- github.com /espressif/esp-idf/commit/00adfb3cbcf9a4a9e6ff1a2b99937a253887f8ca
- github.com /espressif/esp-idf/commit/2fed52c72944781562fb63b8be7b6d29f3cff97e
- github.com /espressif/esp-idf/commit/812f7de59efdf79529e1c10cd788d324fa05f10d
- github.com /espressif/esp-idf/commit/c146056e55815cad542aff640a21e3f94879dd6a
- github.com /espressif/esp-idf/commit/ce902a85135b0e069c125b11735aa8757fb528b2
- github.com /espressif/esp-idf/commit/f9da09de61e98c9074d5cb89d5b1b4c37739fa85
-
github.com
/espressif/esp-idf/security/advisories/GHSA-rjvf-fxv5-x87j
advisory
- github.com /espressif/esp-idf/releases/tag/v5.2.8
- github.com /espressif/esp-idf/releases/tag/v5.3.6
- github.com /espressif/esp-idf/releases/tag/v5.5.6
- github.com /espressif/esp-idf/releases/tag/v6.0.3
Sources
- CVE List CVE-2026-113781
- NVD CVE-2026-113781
- Maintainer advisory GHSA-rjvf-fxv5-x87j
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of espressif/esp-idf published their own advisory on GitHub. Reviewed sources take precedence over it.