{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-49994 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49994 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49994 is a critical missing authorization vulnerability in dannymcc bluehood, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49994 and fix it if it is affected.\n\nWhat it is: CVE-2026-49994 is a critical missing authorization vulnerability in dannymcc bluehood, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49994 in the wild and no public exploit code.\n\nAffected product: dannymcc bluehood. 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-49994/ (Markdown: https://insights.sbomify.com/CVE-2026-49994/index.md)","id":"CVE-2026-49994","markdown":"https://insights.sbomify.com/CVE-2026-49994/index.md","name":"CVE-2026-49994","record":{"aliases":["GHSA-qj2j-wcg3-74jw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Bluetooth monitoring tool","requires_auth":"none","summary":"Attackers can read Bluetooth tracking data and modify application state via unauthenticated API routes when web authentication is enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Bluehood monitors local bluetooth activity. Prior to version 0.7.1, when auth_enabled is set in Bluehood, only the HTML page handlers enforced session validation. The /api/* handlers (settings, devices, groups, per-device endpoints including /api/device/{mac}/notes) called no auth check at all. A network attacker reachable on the dashboard port could read Bluetooth tracking data and modify application state — including the heartbeat URL, prune retention, device groups, and per-device notes — without a session cookie. This issue has been patched in version 0.7.1.","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":"Bluehood: Missing authentication on Bluehood API routes when web auth is enabled","id":"CVE-2026-49994","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Tautulli: Stored Cross-Site Scripting (XSS) in the newsletter","id":"CVE-2026-49995"},"packages":[],"prev":{"headline":"@nuxt/webpack-builder and @nuxt/rspack-builder dev server same-origin check bypassed when Sec-Fetch-Site, Origin, and Referer are all absent (incomplete fix for GHSA-6m52-m754-pw2g)","id":"CVE-2026-49993"},"products":["bluehood"],"published":"2026-09-28","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["dannymcc"]},"summary":"Attackers can read Bluetooth tracking data and modify application state via unauthenticated API routes when web authentication is enabled.","url":"https://insights.sbomify.com/CVE-2026-49994/"}