Skip to main content
CVE-2026-25507VulnerabilityPublished

CVE-2026-25507: espressif esp-idf · Use After Free

Affects espressif esp-idfSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium · fixed in 5.5.3 : update espressif esp-idf when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.5.3
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
espressifesp-idfAffected
  • =5.5.2
  • =5.4.3
  • =5.3.4
  • =5.2.6
  • =5.1.6
Fixed in–
GitHubespressif/esp-idfpkg:github/espressif/esp-idfOther threatsAffected
  • =5.5.2
  • =5.4.3
  • =5.3.4
  • =5.2.6
  • =5.1.6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately update esp-idf to patched versions 5.1.7 or later to remediate the vulnerability. For devices already deployed, firmware updates should be prioritized during maintenance windows. Network segmentation and BLE access controls can reduce exposure by limiting provisioning mode access to trusted personnel or secure environments. Monitoring BLE provisioning activity for unusual connection attempts can help detect exploitation attempts. Developers should review provisioning workflows to avoid enabling keep_ble_on=true unnecessarily and ensure proper lifecycle management of BLE services. Additionally, implementing runtime memory protection and watchdog timers can mitigate impact from unexpected crashes. Device manufacturers should communicate patches and mitigation guidance clearly to downstream integrators and customers.

Description

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.2, 5.4.3, 5.3.4, 5.2.6, and 5.1.6, a use-after-free vulnerability was reported in the BLE provisioning transport (protocomm_ble) layer. The issue can be triggered by a remote BLE client while the device is in provisioning mode. The vulnerability occurred when provisioning was stopped with keep_ble_on = true. In this configuration, internal protocomm_ble state and GATT metadata were freed while the BLE stack and GATT services remained active. Subsequent BLE read or write callbacks dereferenced freed memory, allowing a connected or newly connected client to trigger invalid memory acces. This issue has been patched in versions 5.5.3, 5.4.4, 5.3.5, 5.2.7, and 5.1.7.

References

Community reviews

Loading reviews…