Skip to main content
VulnerabilityPublished

CVE-2026-49994: dannymcc bluehood · Missing Authentication

Affects dannymcc bluehoodSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.7.1 as a priority.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.7.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade bluehood and dannymcc/bluehood to 0.7.1.

Affected software

ProductAffectedFixed in
dannymccbluehoodAffected
  • <0.7.1
Fixed in
  • 0.7.1
GitHubdannymcc/bluehoodpkg:github/dannymcc/bluehoodOther threatsAffected
  • <0.7.1
Fixed in
  • 0.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade bluehood to version 0.7.1 or later, where the missing authentication checks on API endpoints have been fixed. No other mitigation is required as the vendor has provided an official fix.

Description

CVE-2026-49994 is a critical vulnerability in dannymcc bluehood prior to version 0.7.1. When authentication is enabled, only HTML page handlers enforced session validation, while API endpoints under /api/* did not check authentication. This allowed a network attacker with access to the dashboard port to read Bluetooth tracking data and modify application state without a session cookie. The issue is fixed in version 0.7.1.

References

Community reviews

Loading reviews…