# CVE-2025-68474: ESF-IDF Has Out-of-Bounds Write in ESP32 Bluetooth AVRCP Vendor Command Handling

> An out-of-bounds write in the ESP-IDF Bluetooth AVRCP stack allows attackers to cause memory corruption, potentially leading to code execution or crashes on ESP32 devices.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-43gh-7r4f-qp57

## What is CVE-2025-68474?

CVE-2025-68474 is a medium-severity memory corruption vulnerability in espressif esp-idf, published on 26 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.1, 5.4.3, 5.3.4, 5.2.6, 5.1.6, and earlier, in the avrc_vendor_msg() function of the ESP-IDF BlueDroid AVRCP stack, the allocated buffer size was validated using AVRC_MIN_CMD_LEN (20 bytes). However, the actual fixed header data written before the vendor payload exceeds this value. This totals 29 bytes written before p_msg->p_vendor_data is copied. Using the old AVRC_MIN_CMD_LEN could allow an out-of-bounds write if vendor_len approaches the buffer limit. For commands where vendor_len is large, the original buffer allocation may be insufficient, causing writes beyond the allocated memory. This can lead to memory corruption, crashes, or other undefined behavior. The overflow could be larger when assertions are disabled.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-68474?

It affects 1 product.


Products: Espressif Esp-Idf.

## How do I fix CVE-2025-68474?

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

## Is CVE-2025-68474 being exploited?

There is no known exploitation of CVE-2025-68474 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-2025-68474 and fix it if it is affected.

What it is: CVE-2025-68474 is a medium-severity memory corruption vulnerability in espressif esp-idf, published on 26 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68474 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-2025-68474/ (Markdown: https://insights.sbomify.com/CVE-2025-68474/index.md)
```

## Sources

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

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