{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-37100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-37100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-37100 is a medium-severity authentication bypass vulnerability in n/a, published on 16 Apr 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-37100 and fix it if it is affected.\n\nWhat it is: CVE-2026-37100 is a medium-severity authentication bypass vulnerability in n/a, published on 16 Apr 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-37100 in the wild and no public exploit code.\n\nAffected product: n/a. 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-37100/ (Markdown: https://insights.sbomify.com/CVE-2026-37100/index.md)","id":"CVE-2026-37100","markdown":"https://insights.sbomify.com/CVE-2026-37100/index.md","name":"CVE-2026-37100","record":{"aliases":["GHSA-c9qp-qc83-7rwj"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yamaha sound bar","requires_auth":"none","summary":"Remote attackers within Bluetooth range can connect to the Yamaha SR-B30A sound bar without authentication via the BLE control interface.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue in the Bluetooth Low Energy (BLE) control interface of the Yamaha SR-B30A sound bar firmware 2.40 (Mobile App: Sound Bar Remote / version: 2.40) allows remote attackers within BLE radio range to connect without authentication via the Sound Bar Remote protocol","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":"Auth bypass in n/a","id":"CVE-2026-37100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2026-37106"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2026-37073"},"products":["n/a"],"published":"2026-04-16","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-04-18","vendors":["n/a"]},"summary":"Remote attackers within Bluetooth range can connect to the Yamaha SR-B30A sound bar without authentication via the BLE control interface.","url":"https://insights.sbomify.com/CVE-2026-37100/"}