# CVE-2026-22099: EVbee DC-80 improper authentication in Bluetooth interface

Source: https://junglewise.ai/threats/cve-2026-22099-evbee-dc-80-improper-authentication-in-bluetooth-interface  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-13. Updated: 2026-07-13  
License: CC BY 4.0 with a link back

CVE-2026-22099 · Severity: info · CVSS 8.7 · Published 2026-07-13

A security flaw in EVbee DC-80 electric vehicle charging stations allows unauthorized individuals within Bluetooth range to control the device. An attacker could force the station to reboot, steal sensitive information, or redirect the device to install malicious software updates. This could lead to service disruptions for customers and potential long-term compromise of the charging infrastructure.

Technologies: [EVbee DC-80](https://junglewise.ai/threats/technologies/dc-80). Vendors: [EVbee](https://junglewise.ai/threats/vendors/evbee).

## Quick answers

**Is CVE-2026-22099 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-22099 being exploited in the wild.

**How severe is CVE-2026-22099?** Informational severity, with a CVSS score of 8.7, published 13 July 2026.

**Which products and versions are affected?** EVbee DC-80 versions before 1.5.4.

**Is there a fix for CVE-2026-22099?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-22099 attacked?** It is attacked from the adjacent network, in a network appliance.

**Am I affected by CVE-2026-22099?** Check whether you run EVbee DC-80 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The EVbee DC-80 charging station suffers from improper authentication (CWE-287) in its Bluetooth communication interface. An attacker within physical proximity (Bluetooth range) can issue commands without providing credentials. This exposed functionality allows for sensitive information leakage, the ability to trigger device reboots (denial of service), and the capability to push a rogue firmware update URL to the device. The vulnerability is addressed in version 1.5.4.

## Affected products

- EVbee DC-80 versions before 1.5.4

## Timeline

- 2026-07-13: advisory: CVE-2026-22099 published by NVD and DIVD

## References

- [https://csirt.divd.nl/DIVD-2026-00001/](https://csirt.divd.nl/DIVD-2026-00001/)

## Related threats

- [EVbee DC-80 weak hardcoded root password in SSH](https://junglewise.ai/threats/cve-2026-22094-the-firmware-for-the-evbee-dc-80-has-a-weak-hardcoded-root)
- [EVbee DC-80 command injection in NPC start endpoint](https://junglewise.ai/threats/cve-2026-22103-evbee-dc-80-command-injection-in-npc-start-endpoint)
- [EVbee DC-80 arbitrary file write via webserver endpoint](https://junglewise.ai/threats/cve-2026-22102-evbee-dc-80-arbitrary-file-write-via-webserver-endpoint)
- [EVbee DC-80 command injection in OCPP ReserveLogin](https://junglewise.ai/threats/cve-2026-22100-evbee-dc-80-command-injection-in-ocpp-reservelogin)
- [EVbee DC-80 missing signature validation in firmware update](https://junglewise.ai/threats/cve-2026-22097-evbee-dc-80-missing-signature-validation-in-firmware-update)