{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-65933 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-65933 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-65933 is a medium-severity vulnerability in silabs.com BT122, published on 13 Aug 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-65933 and fix it if it is affected.\n\nWhat it is: CVE-2026-65933 is a medium-severity vulnerability in silabs.com BT122, published on 13 Aug 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-65933 in the wild and no public exploit code.\n\nAffected product: silabs.com BT122. 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-65933/ (Markdown: https://insights.sbomify.com/CVE-2026-65933/index.md)","id":"CVE-2026-65933","markdown":"https://insights.sbomify.com/CVE-2026-65933/index.md","name":"CVE-2026-65933","record":{"aliases":["GHSA-pmcm-gw2w-hpxf"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bluetooth module","requires_auth":"none","summary":"A malformed Bluetooth connection request can cause the BT122 module to leak sensitive information, requiring a firmware patch.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Silabs","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-126","name":"Buffer Over-read"}],"description":"A malformed Bluetooth connection request message can cause the BT122 to leak potentially sensitive information. See vulnerability B-E4 in the related paper below.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"BT122 malformed packet with increased length field causes memory leak","id":"CVE-2026-65933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"BT122 plaintext pause encryption request causes DOS","id":"CVE-2026-65934"},"packages":[],"prev":{"headline":"BT122 stops advertising","id":"CVE-2026-65932"},"products":["BT122"],"published":"2026-08-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-08-13","vendors":["silabs.com"]},"summary":"A malformed Bluetooth connection request can cause the BT122 module to leak sensitive information, requiring a firmware patch.","url":"https://insights.sbomify.com/CVE-2026-65933/"}