Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-49994 – Authentication Bypass on API Endpoints – Bluehood ≤ 0.7.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-49994 is a critical missing-authentication vulnerability affecting Bluehood, a self-hosted Bluetooth activity monitoring tool. Although Bluehood’s HTML page handlers correctly enforced session validation when authentication was enabled, its /api/* endpoints performed no authentication checks at all, allowing any unauthenticated network attacker to read Bluetooth tracking data and modify application configuration. The flaw carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: Authentication was implemented inconsistently across Bluehood’s web interface. Session validation was applied only to HTML page routes; the /api/* route handlers called no authentication or authorization check whatsoever, even when auth_enabled was configured.
  • Trigger conditions: Any network-reachable request to an affected API endpoint succeeds without a valid session cookie or credentials, regardless of the server’s authentication configuration.
  • Attack vector: Network (AV:N), low attack complexity, no privileges or user interaction required — a remote, unauthenticated attacker with network access to the Bluehood dashboard port can exploit the issue directly.
  • Impact: Full disclosure of collected Bluetooth observation/tracking data (device presence, patterns, groupings, notes) and unauthorized modification of application settings, including heartbeat URLs, data retention policies, device groupings, and per-device notes. No availability impact was noted.
  • Affected endpoints: /api/settings, /api/devices, /api/groups, /api/device/{mac}/notes, and other per-device API endpoints.

Affected software

  • Bluehood (dannymcc/bluehood) — all versions up to and including 0.7.0
  • Fixed in version 0.7.1

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Bluehood to version 0.7.1 or later, which introduces a default-deny authentication middleware that gates every route on a valid session, exempting only the required authentication endpoints (/login, /api/auth/login, /api/auth/logout, /api/auth/status, /api/auth/setup).
  • If immediate patching is not possible:
    • Place the Bluehood dashboard behind a reverse proxy that enforces its own authentication (e.g., an OAuth-based access proxy).
    • Restrict network access to the Bluehood dashboard/API port to trusted internal networks only; do not expose it directly to the internet.
    • Audit device data and configuration settings (heartbeat URLs, retention policies, groupings, notes) for unauthorized changes if the instance was internet-reachable prior to patching.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge