{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25507 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25507 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25507 is a medium-severity use after free 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."},"fix_prompt":"Check this codebase for CVE-2026-25507 and fix it if it is affected.\n\nWhat it is: CVE-2026-25507 is a medium-severity use after free 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.\nExploitation: There is no known exploitation of CVE-2026-25507 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-25507/ (Markdown: https://insights.sbomify.com/CVE-2026-25507/index.md)","id":"CVE-2026-25507","markdown":"https://insights.sbomify.com/CVE-2026-25507/index.md","name":"CVE-2026-25507","record":{"aliases":["GHSA-h7r3-gmg9-xjmg"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Espressif IoT framework","requires_auth":"none","summary":"A remote attacker can trigger a use-after-free in BLE provisioning, potentially causing crashes or executing code on affected IoT devices.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"esp-idf","vendor":"espressif"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"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, 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.","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 Has Use-after-free Vulnerability in BLE Provisioning","id":"CVE-2026-25507","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ESF-IDF Has Memory Safety Vulnerabilities in BLE Provisioning","id":"CVE-2026-25508"},"packages":[],"prev":{"headline":"MUNGE has a buffer overflow in message unpacking allows key leakage and credential forgery","id":"CVE-2026-25506"},"products":["esp-idf"],"published":"2026-02-04","related":[{"cvss_score":9.3,"headline":"ESF-IDF: Out-of-Bounds Write in ESP-TEE Secure Service Wrappers","id":"CVE-2026-45328","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2024-53406","kev_date_added":null,"published":"2025-03-13"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28139","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2024-33453","kev_date_added":null,"published":"2024-10-17"},{"cvss_score":8.1,"headline":"Weak cryptography in n/a","id":"CVE-2019-12587","kev_date_added":null,"published":"2019-09-04"},{"cvss_score":7.5,"headline":"ESF-IDF: Remote Null Pointer Dereference in WebSocket Server","id":"CVE-2026-45541","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-51428","kev_date_added":null,"published":"2024-11-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-02-04","vendors":["espressif"]},"summary":"A remote attacker can trigger a use-after-free in BLE provisioning, potentially causing crashes or executing code on affected IoT devices.","url":"https://insights.sbomify.com/CVE-2026-25507/"}