# CVE-2026-25508: ESF-IDF Has Memory Safety Vulnerabilities in BLE Provisioning

> Remote attackers can trigger memory corruption in Espressif IoT devices during BLE provisioning via out-of-bounds reads, potentially leading to code execution or crashes.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-9j5x-rf36-54x9

## What is CVE-2026-25508?

CVE-2026-25508 is a medium-severity memory corruption vulnerability in espressif esp-idf, published on 4 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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, an out-of-bounds read vulnerability was reported in the BLE ATT Prepare Write handling of the BLE provisioning transport (protocomm_ble). The issue can be triggered by a remote BLE client while the device is in provisioning mode. The transport accumulated prepared-write fragments in a fixed-size buffer but incorrectly tracked the cumulative length. By sending repeated prepare write requests with overlapping offsets, a remote client could cause the reported length to exceed the allocated buffer size. This inflated length was then passed to provisioning handlers during execute-write processing, resulting in an out-of-bounds read and potential memory corruption. This issue has been patched in versions 5.5.3, 5.4.4, 5.3.5, 5.2.7, and 5.1.7.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-25508?

It affects 1 product.


Products: Espressif Esp-Idf.

## How do I fix CVE-2026-25508?

No fix has been published for CVE-2026-25508 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25508 being exploited?

There is no known exploitation of CVE-2026-25508 in the wild and no public exploit code.

## Other vulnerabilities in espressif esp-idf

- [CVE-2026-45328](https://insights.sbomify.com/CVE-2026-45328/): ESF-IDF: Out-of-Bounds Write in ESP-TEE Secure Service Wrappers (critical 9.3)
- [CVE-2024-53406](https://insights.sbomify.com/CVE-2024-53406/): Auth bypass in n/a (high 8.8)
- [CVE-2021-28139](https://insights.sbomify.com/CVE-2021-28139/): Memory corruption in n/a (high 8.8)
- [CVE-2024-33453](https://insights.sbomify.com/CVE-2024-33453/): Information disclosure in n/a (high 8.1)
- [CVE-2019-12587](https://insights.sbomify.com/CVE-2019-12587/): Weak cryptography in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25508 and fix it if it is affected.

What it is: CVE-2026-25508 is a medium-severity memory corruption vulnerability in espressif esp-idf, published on 4 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25508 in the wild and no public exploit code.

Affected product: espressif esp-idf. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25508/ (Markdown: https://insights.sbomify.com/CVE-2026-25508/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25508
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25508
- OSV: https://osv.dev/vulnerability/CVE-2026-25508

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25508/
Summaries are generated and may contain mistakes; the official description above is the record.