CVE-2026-22093: Adversary-in-the-Middle (AitM) attack vulnerability in EVbee Service app
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.
Security readout for executives and security teams
Plain-English summary
EVbee Service for Android v1.4.101.00 does not properly check the server certificate, so a network-path attacker could intercept app traffic. Because some traffic is also weakly encrypted with RC4 and a hardcoded key, charging-station access codes may be exposed or altered.
Executive priority
Treat this as urgent for EVbee operators because compromise could expose or manipulate charging-station access codes. Prioritize inventory, containment, and vendor guidance review, especially for fleets or public charging operations using the affected Android app.
Technical view
The issue is a CWE-295 certificate validation failure in EVbee Service v1.4.101.00. The advisory states HTTPS is used but server certificates are not validated, enabling AitM interception and manipulation. Traffic is additionally protected with RC4 using a hardcoded key, weakening confidentiality for communications including charging-station access codes.
Likely exposure
Exposure is most likely where EVbee Service Android app v1.4.101.00 is used to manage or access EVbee charging stations, especially over networks where an attacker could sit on the communication path.
Exploitation context
No active exploitation is stated in the source bundle, and the CVE is not marked KEV. The described attack requires a network-path position between the app and EVbee server, but does not require app privileges or user interaction once that position exists.
Researcher notes
The public bundle identifies the affected app version and vulnerability class, but does not provide a patch, fixed version, or exploitation evidence. Avoid assuming wider EVbee product impact beyond EVbee Service Android app v1.4.101.00.
Mitigation direction
Check EVbee and DIVD guidance for fixed versions or official workarounds.
Inventory and remove or restrict EVbee Service v1.4.101.00 where possible.
Avoid using the affected app on untrusted or shared networks.
Review and rotate charging-station access codes if exposure is suspected.
Monitor charging-station access logs for unusual or unauthorized activity.
Validation and detection
Confirm whether EVbee Service v1.4.101.00 is installed on managed Android devices.
Identify business processes depending on the affected app for charging-station access.
Review network conditions where the app is commonly used.
Check vendor or DIVD advisories for updates after July 16, 2026.
Assess whether charging-station access codes may have traversed exposed app sessions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-295 · source CWE mapping
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.