Answer in brief
CVE-2026-22093 records a Critical severity (CVSS 9.5) vulnerability in Adversary-in-the-Middle (AitM) attack vulnerability in EVbee Service app. The current sources do not mark it as known exploited. The current feed maps EVbee/EVbee Service (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps EVbee/EVbee Service (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| EVbee/EVbee Servicegeneric | >=0 <1.4.7.10 | 1.4.7.10 |
Published upstream
Jul 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 13, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-22093 records a Critical severity (CVSS 9.5) vulnerability in Adversary-in-the-Middle (AitM) attack vulnerability in EVbee Service app. The current sources do not mark it as known exploited. The current feed maps EVbee/EVbee Service (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps EVbee/EVbee Service (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| EVbee/EVbee Servicegeneric | >=0 <1.4.7.10 | 1.4.7.10 |
Published upstream
Jul 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 13, 2026
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.
Quoted source text, attributed separately from HOL analysis.