CVE-2026-22093

CRITICALPre-NVD 9.59.5—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% 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: epss, secondary
Trending — 4 sources updated this week
9.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.5Exploit: NoneExposed: 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)
EPSS
10.3%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 13, 2026

Advisory Details (1)

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

Redirecting…

https://csirt.divd.nl/DIVD-2026-00001/

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 39× in last 7d / 39× 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-15 23:23 UTCEG score recompute
  2. 2026-07-15 23:23 UTCGHSA enrichment
  3. 2026-07-15 19:32 UTCEG score recompute
  4. 2026-07-15 19:32 UTCGHSA enrichment
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 15:41 UTCEG score recompute
  8. 2026-07-15 15:41 UTCGHSA enrichment
  9. 2026-07-15 11:51 UTCEG score recompute
  10. 2026-07-15 11:51 UTCGHSA enrichment
  11. 2026-07-15 08:01 UTCEG score recompute
  12. 2026-07-15 08:01 UTCGHSA enrichment
  13. 2026-07-15 04:11 UTCEG score recompute
  14. 2026-07-15 04:10 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 00:15 UTCEG score recompute
  18. 2026-07-15 00:15 UTCGHSA enrichment
  19. 2026-07-14 20:24 UTCEG score recompute
  20. 2026-07-14 20:24 UTCGHSA enrichment
  21. 2026-07-14 16:34 UTCEG score recompute
  22. 2026-07-14 16:34 UTCGHSA enrichment
  23. 2026-07-14 12:44 UTCEG score recompute
  24. 2026-07-14 12:44 UTCGHSA enrichment
  25. 2026-07-14 08:54 UTCEG score recompute
Show 14 more
  1. 2026-07-14 08:54 UTCGHSA enrichment
  2. 2026-07-14 05:04 UTCEG score recompute
  3. 2026-07-14 05:04 UTCGHSA enrichment
  4. 2026-07-14 01:14 UTCEG score recompute
  5. 2026-07-14 01:14 UTCGHSA enrichment
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 21:24 UTCEG score recompute
  8. 2026-07-13 21:24 UTCGHSA enrichment
  9. 2026-07-13 17:34 UTCEG score recompute
  10. 2026-07-13 17:34 UTCGHSA enrichment
  11. 2026-07-13 13:44 UTCEG score recompute
  12. 2026-07-13 13:44 UTCGHSA enrichment
  13. 2026-07-13 09:53 UTCEG score recompute
  14. 2026-07-13 09:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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. 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 10.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22093?
CVE-2026-22093 has a CVSS v3 base score of 9.5 (NVD).
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.

Start Free Scan →Browse All CVEs