NVD / CVE Program· CNA GitHub_M

CVE-2026-25507: ESF-IDF Has Use-after-free Vulnerability in BLE Provisioning

MediumCVSS 6.3 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 25/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
Someone on the same network segment can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
No fixed version is recorded, but the references include a patch (commit or PR) link.

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Feb 4, 2026
Updated: Jun 17, 2026
EPSS: 0.2% · 14th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 25 / 40 · 6.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.3
CNA · GitHub_M: 6.3; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
espressif	esp-idf	cpe:2.3:a:espressif:esp-idf

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

espressif esp-idf
- = 5.5.2, = 5.4.3, = 5.3.4, = 5.2.6, = 5.1.6affected

Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

espressif esp-idf5.1.6
espressif esp-idf5.2.6
espressif esp-idf5.3.4
espressif esp-idf5.4.3
espressif esp-idf5.5.2

Same product

espressif: all records

Other highest-scoring records for the same primary product.

CVE-2026-113780ESF-IDF: Unvalidated Stack Pointer at the ESP-TEE Privilege-Switch Boundary
37Monitor
CVE-2026-45328ESF-IDF: Out-of-Bounds Write in ESP-TEE Secure Service Wrappers
35Monitor
CVE-2024-53406Espressif Esp idf v5.3.0 is vulnerable to Insecure Permissions resulting in Authentication bypass.
35Monitor

Published before and after this one in the same product

← EarlierCVE-2025-68473Dec 27, 2025 · ESF-IDF Has Out-of-Bounds Read in ESP32 Bluetooth SDP Result Handling
0Monitor
← EarlierCVE-2025-68474Dec 27, 2025 · ESF-IDF Has Out-of-Bounds Write in ESP32 Bluetooth AVRCP Vendor Command Handling
24Monitor
Later →CVE-2026-25508Feb 4, 2026 · ESF-IDF Has Memory Safety Vulnerabilities in BLE Provisioning
25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Someone on the same network segment can trigger it.
No account or password is required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: low · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Adjacent
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: None
Integrity impact: Low
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

github.com/espressif/esp-idf/commit/0540c85140c2c06c0cbecc8843277ea676d5c4a9

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records