CVE-2026-22093 Adversary-in-the-Middle (AitM) attack vulnerability in EVbee Service app
Attackers can intercept and manipulate EVbee Service app traffic due to missing certificate validation and weak RC4 encryption, exposing charging station access codes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-22093?
CVE-2026-22093 is a critical vulnerability in EVbee Service, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The EVbee Service Android app uses TLS encrypted communication (HTTPS), but does not validate the certificate provided by the server. This allows an attacker on the network path between the app and EVbee server to intercept and manipulate the communication between the app and server. The traffic is weakly encrypted using RC4 with a hardcoded key, which allows an attacker to gain access to the communication. Part of this communication involves access codes to charging stations.
This issue affects EVbee Service: v1.4.101.00.
Weakness: CWE-295
Which versions are affected by CVE-2026-22093?
How do I fix CVE-2026-22093?
No fix has been published for CVE-2026-22093 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-22093 being exploited?
There is no known exploitation of CVE-2026-22093 in the wild and no public exploit code.
Sources
Also known as GHSA-8rgr-qqgf-gmfw.