CVE-2026-113781

HIGHPre-NVD 7.17.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source

Also known asEUVD-2026-127194 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1HIGHlow confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 17, 2026

Last Modified

November 17, 2026

Advisory Details (10)

Auto-updated Nov 17, 2026
Patch available. Sources: github_commit, github_release.
GitHub release Patch Available

ESP-IDF Release v6.0.3

Patch available: espressif/esp-idf v6.0.3

https://github.com/espressif/esp-idf/releases/tag/v6.0.3
GitHub release Patch Available

ESP-IDF Release v5.5.6

Patch available: espressif/esp-idf v5.5.6

https://github.com/espressif/esp-idf/releases/tag/v5.5.6
GitHub release Patch Available

ESP-IDF Release v5.3.6

Patch available: espressif/esp-idf v5.3.6

https://github.com/espressif/esp-idf/releases/tag/v5.3.6
GitHub release Patch Available

ESP-IDF Release v5.2.8

Patch available: espressif/esp-idf v5.2.8

https://github.com/espressif/esp-idf/releases/tag/v5.2.8
GitHub commit

commit f9da09de61e9 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit f9da09de61e9 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/f9da09de61e98c9074d5cb89d5b1b4c37739fa85
GitHub commit

commit ce902a85135b (espressif/esp-idf)

Fix landed in espressif/esp-idf commit ce902a85135b — awaiting tagged release

https://github.com/espressif/esp-idf/commit/ce902a85135b0e069c125b11735aa8757fb528b2
GitHub commit

commit c146056e5581 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit c146056e5581 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/c146056e55815cad542aff640a21e3f94879dd6a
GitHub commit

commit 812f7de59efd (espressif/esp-idf)

Fix landed in espressif/esp-idf commit 812f7de59efd — awaiting tagged release

https://github.com/espressif/esp-idf/commit/812f7de59efdf79529e1c10cd788d324fa05f10d
GitHub commit

commit 2fed52c72944 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit 2fed52c72944 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/2fed52c72944781562fb63b8be7b6d29f3cff97e
GitHub commit

commit 00adfb3cbcf9 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit 00adfb3cbcf9 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/00adfb3cbcf9a4a9e6ff1a2b99937a253887f8ca

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-11-19 11:26 UTCOSV refresh
  5. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-17 23:28 UTCEchelonGraph re-scored
  7. 2026-11-17 22:33 UTCEchelonGraph re-scored
  8. 2026-11-17 20:03 UTCENISA EUVD ID recordedEUVD-2026-127194 · Source: ENISA EUVD
  9. 2026-11-17 19:19 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  10. 2026-11-17 19:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-113781?
CVE-2026-113781 is a high-severity vulnerability; its CVE record was published on November 17, 2026. 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…
When was the CVE record for CVE-2026-113781 published?
The CVE record for CVE-2026-113781 was published on November 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-113781 actively exploited?
CVE-2026-113781 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113781?
CVE-2026-113781 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-113781?
A fix for CVE-2026-113781 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-113781

Explore →

Is Your Infrastructure Affected by CVE-2026-113781?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.