Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEnter Bluetooth radio range of target device
-
DeliveryAuthenticate or pair with device (low-privilege pairing)
-
ExploitSend malformed AVRCP vendor command with zero-length payload
-
Executionavrc_pars_vendor_cmd() dereferences buffer pointer without length check
-
PersistRead one byte past buffer boundary
-
ImpactLeak adjacent memory byte or trigger parser fault degrading availability
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must be within Bluetooth radio range of the target device (AV:A - Adjacent vector). The CVSS vector specifies PR:L (low privileges required), indicating the exploit requires some level of Bluetooth authentication or an established pairing relationship; fully anonymous unauthenticated exploitation is not confirmed by the available CVSS data. The device must have the AVRCP target profile enabled in its BlueDroid Bluetooth stack configuration - this is the specific feature that makes avrc_pars_vendor_cmd() reachable; devices with AVRCP target disabled are not exposed. Exploitation is further limited to the five specific ESP-IDF point releases named in the advisory (5.2.6, 5.3.5, 5.4.4, 5.5.3, 6.0) and does not apply to devices using alternative Bluetooth stacks. |
| Impact | The CVSS 4.6 score appropriately reflects meaningful but constrained real-world risk. The attack vector is Adjacent (AV:A), requiring the attacker to be within Bluetooth radio range - a significant physical constraint that limits mass exploitation potential compared to internet-exposed vulnerabilities. Low complexity (AC:L) and no user interaction (UI:N) mean the attack could be scripted and repeatable once proximity is achieved, but the PR:L privilege requirement indicates some Bluetooth authentication or pairing context is needed, not a fully anonymous attack. Impact is bounded: partial confidentiality loss (C:L, likely a few leaked memory bytes) and partial availability impact (A:L, potential parser fault or crash) with no integrity impact (I:N). No EPSS data was provided in the input, and the CVE is absent from CISA KEV, indicating no confirmed active exploitation. For most deployments this is a medium-priority patch-cycle item, but IoT devices operating in shared Bluetooth environments - factories, retail, consumer electronics - warrant faster remediation given the low physical barrier in those contexts. No conflict exists between the CVSS vector and the description. |
| Exploit ScenarioDerived | An attacker positions themselves within Bluetooth range of an ESP32 device running an affected ESP-IDF version, authenticates or pairs at a low privilege level, and transmits a crafted AVRCP GET_CAPABILITIES or LIST_APPLICATION_SETTING_VALUES vendor command with a zero-length parameter payload. The parser in avrc_pars_vendor_cmd() dereferences the buffer pointer without the length guard, reading one byte beyond the allocated buffer - potentially disclosing an adjacent memory byte or triggering a fault that degrades Bluetooth stack availability. No public proof-of-concept exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 10, 2026
Out-of-bounds read in ESP-IDF's BlueDroid AVRCP vendor-command parser allows adjacent Bluetooth attackers with low privileges to leak device memory and degrade availability across multiple ESP-IDF stable branches. Versions 5.2.6, 5.3.5, 5.4.4, 5.5.3, and 6.0 are confirmed affected via the Espressif GitHub security advisory. The parser's failure to validate payload length before dereferencing the buffer pointer enables a malformed AVRCP vendor command to read beyond allocated memory, yielding partial confidentiality loss and potential stack instability. No public exploit code exists and this CVE is not in CISA KEV at time of analysis.
RemediationAI
Upgrade to the corresponding patched release for your branch: 5.2.7, 5.3.6, 5.4.5, 5.5.4, or 6.0.1, as documented in the Espressif security advisory at https://github.com/espressif/esp-idf/security/advisories/GHSA-3pp8-42fh-3j3c. Fix commits covering each stable branch are available at commits 56053c4d, 60f9362f, 7c004d3f, 8746e5f7, b0959b5a, and c53d05ae in the ESP-IDF GitHub repository. If firmware upgrades cannot be deployed immediately, disabling AVRCP target profile support in the device's Bluetooth stack configuration removes the vulnerable code path entirely; the trade-off is loss of audio remote control functionality, which may be acceptable for non-audio IoT devices. Restricting Bluetooth discoverability and pairing to trusted devices raises the bar for exploitation given the PR:L requirement, though it does not eliminate the vulnerability if a compromised or malicious paired device is present.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is in avrc_pars_vendor_cmd() within components/bt/host/bluedroid/stack/avrc/avrc_pars_tg.c - the AVRCP (Audio/Video Remote Control Profile) target-side vendor command parser in Espressif's BlueDroid Bluetooth stack. CWE-125 (Out-of-Bounds Read) precisely describes the root cause: two command handlers - GET_CAPABILITIES and LIST_APPLICATION_SETTING_VALUES - dereferenced the buffer pointer p via *p++ before validating that the length field len was at least 1. If a peer sends a vendor command with a zero-length payload, the dereference reads one byte past the end of the valid buffer region. The commit diff confirms the fix pattern: a len < 1 guard was inserted ahead of each dereference. CPE cpe:2.3:a:espressif:esp-idf:*:*:*:*:*:*:*:* covers the affected framework. The issue is isolated to the BlueDroid stack and does not affect alternative Bluetooth stack implementations.
Know when Esp Idf gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
DescriptionCVE.org
ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.2.6, 5.3.5, 5.4.4, 5.5.3, and 6.0, an out-of-bounds read exists in the BlueDroid AVRCP vendor-command parser (avrc_pars_vendor_cmd() in components/bt/host/bluedroid/stack/avrc/avrc_pars_tg.c). This issue has been patched in versions 5.2.7, 5.3.6, 5.4.5, 5.5.4, and 6.0.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in ESP-IDF Memory Safety and Input Validation Flaws
View all 6Espressif Esp idf v5.3.0 is vulnerable to Insecure Permissions resulting in Authentication bypass. Rated high severity (
The EAP peer implementation in Espressif ESP-IDF 2.0.0 through 4.0.0 and ESP8266_NONOS_SDK 2.2.0 through 3.1.0 allows th
An encryption-bypass issue was discovered on Espressif ESP-IDF devices through 4.2, ESP8266_NONOS_SDK devices through 3.
Buffer Overflow vulnerability in esp-idf v.5.1 allows a remote attacker to execute arbitrary code via a crafted script t
The EAP peer implementation in Espressif ESP-IDF 2.0.0 through 4.0.0 and ESP8266_NONOS_SDK 2.2.0 through 3.1.0 processes
A security vulnerability in the ESP-NOW protocol implementation within the ESP Wi-Fi component of (CVSS 9.8). Critical s
ESP-IDF is the official development framework for Espressif SoCs. Rated high severity (CVSS 8.8), this vulnerability is
The Bluetooth Classic implementation in Espressif ESP-IDF 4.4 and earlier does not properly restrict the Feature Page up
Buffer Overflow vulnerability in esp-idf v.5.1 allows a remote attacker to obtain sensitive information via the external
Denial of service in Espressif's ESP-IDF JPEG driver (versions 6.0.1, 5.5.4, 5.4.4, 5.3.5 and likely earlier) stems from
EUVD-2026-35919
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB