{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81507 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81507 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81507 is a medium-severity vulnerability in espressif esp-idf, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81507 and fix it if it is affected.\n\nWhat it is: CVE-2026-81507 is a medium-severity vulnerability in espressif esp-idf, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81507 in the wild and no public exploit code.\n\nAffected product: espressif esp-idf. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81507/ (Markdown: https://insights.sbomify.com/CVE-2026-81507/index.md)","id":"CVE-2026-81507","markdown":"https://insights.sbomify.com/CVE-2026-81507/index.md","name":"CVE-2026-81507","record":{"aliases":["GHSA-v335-fxwc-rc44"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ESP-IDF Bluetooth stack","requires_auth":"none","summary":"Remote attackers can read sensitive Bluetooth stack memory via malformed L2CAP requests in ESP-IDF, requiring an upgrade to patched versions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. Prior to 5.2.8, 5.3.6, 5.5.5, 6.0.3, and 6.1-rc1, ESP-IDF BlueDroid L2CAP configuration-option processing in l2c_main.c and l2c_utils.c does not consistently validate option lengths against the remaining received packet bytes. A remote unauthenticated BR/EDR peer within radio range can send a malformed L2CAP configuration request that causes an out-of-bounds read, and under some runtime conditions limited adjacent Bluetooth stack memory can be included in an outbound L2CAP Configuration Response. The issue affects ESP32-class products using the BlueDroid host stack with Classic Bluetooth enabled. This issue is fixed in 5.2.8, 5.3.6, 5.5.5, 6.0.3, and 6.1-rc1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ESF-IDF: Bluetooth Classic L2CAP Heap Memory Disclosure Allowing Unauthorized Access to Sensitive Data","id":"CVE-2026-81507","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":13,"next":{"headline":"ESF-IDF: Heap Out-of-Bounds Read in Bluedroid A2DP Sink Media Packet Processing","id":"CVE-2026-81508"},"packages":[],"prev":{"headline":"Convoy: Cross-Tenant Source IDOR Leaks Plaintext Message Broker Credentials","id":"CVE-2026-81505"},"products":["esp-idf"],"published":"2026-10-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["espressif"]},"summary":"Remote attackers can read sensitive Bluetooth stack memory via malformed L2CAP requests in ESP-IDF, requiring an upgrade to patched versions.","url":"https://insights.sbomify.com/CVE-2026-81507/"}