CVE-2026-22093

CRITICALPre-NVD 9.59.5
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:divd, epss
Trending — 3 sources updated this week
9.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.5
EG Score
9.5(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity95% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 16, 2026

Advisory Details (1)

Auto-updated Jul 13, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-22093(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-28 21:01 UTCGHSA enrichment
  2. 2026-07-28 17:11 UTCEG score recompute
  3. 2026-07-28 17:10 UTCGHSA enrichment
  4. 2026-07-28 12:09 UTCGHSA enrichment
  5. 2026-07-28 08:09 UTCGHSA enrichment
  6. 2026-07-28 04:17 UTCGHSA enrichment
  7. 2026-07-28 00:27 UTCGHSA enrichment
  8. 2026-07-27 19:51 UTCGHSA enrichment
  9. 2026-07-27 15:25 UTCEG score recompute
  10. 2026-07-27 15:25 UTCGHSA enrichment
  11. 2026-07-27 14:13 UTCEPSS rescore
  12. 2026-07-27 11:17 UTCGHSA enrichment
  13. 2026-07-27 07:26 UTCGHSA enrichment
  14. 2026-07-27 03:35 UTCGHSA enrichment
  15. 2026-07-26 23:26 UTCGHSA enrichment
  16. 2026-07-26 19:35 UTCGHSA enrichment
  17. 2026-07-26 15:44 UTCEG score recompute
  18. 2026-07-26 15:44 UTCGHSA enrichment
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 11:54 UTCEG score recompute
  22. 2026-07-26 11:54 UTCGHSA enrichment
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-25 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
Show 46 more
  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:06 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-19 02:28 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-17 06:10 UTCGHSA enrichment
  15. 2026-07-17 02:20 UTCGHSA enrichment
  16. 2026-07-16 22:28 UTCGHSA enrichment
  17. 2026-07-16 18:38 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-07-16 14:47 UTCGHSA enrichment
  21. 2026-07-16 10:54 UTCGHSA enrichment
  22. 2026-07-16 07:04 UTCGHSA enrichment
  23. 2026-07-16 03:13 UTCGHSA enrichment
  24. 2026-07-15 23:23 UTCGHSA enrichment
  25. 2026-07-15 19:32 UTCGHSA enrichment
  26. 2026-07-15 16:57 UTCEPSS rescore
  27. 2026-07-15 16:57 UTCEPSS rescore
  28. 2026-07-15 15:41 UTCGHSA enrichment
  29. 2026-07-15 11:51 UTCGHSA enrichment
  30. 2026-07-15 08:01 UTCGHSA enrichment
  31. 2026-07-15 04:10 UTCGHSA enrichment
  32. 2026-07-15 02:00 UTCEPSS rescore
  33. 2026-07-15 02:00 UTCEPSS rescore
  34. 2026-07-15 00:15 UTCGHSA enrichment
  35. 2026-07-14 20:24 UTCGHSA enrichment
  36. 2026-07-14 16:34 UTCGHSA enrichment
  37. 2026-07-14 12:44 UTCGHSA enrichment
  38. 2026-07-14 08:54 UTCGHSA enrichment
  39. 2026-07-14 05:04 UTCGHSA enrichment
  40. 2026-07-14 01:14 UTCGHSA enrichment
  41. 2026-07-13 22:30 UTCEPSS rescore
  42. 2026-07-13 21:24 UTCGHSA enrichment
  43. 2026-07-13 17:34 UTCGHSA enrichment
  44. 2026-07-13 13:44 UTCGHSA enrichment
  45. 2026-07-13 09:53 UTCEG score recompute
  46. 2026-07-13 09:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-22093?
CVE-2026-22093 is a critical vulnerability published on July 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…
When was CVE-2026-22093 disclosed?
CVE-2026-22093 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22093 actively exploited?
CVE-2026-22093 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-22093?
CVE-2026-22093 has a CVSS v4.0 base score of 9.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-22093?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22093, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-22093

Explore →

Is Your Infrastructure Affected by CVE-2026-22093?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.