CVE-2026-22099

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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

The charging station does not require authentication for Bluetooth commands to perform actions. The functionality exposed includes sensitive information leakage, triggering reboots, or pushing a firmware update URL.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
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-22099(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 19× in last 7d / 102× 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.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-08-30 05:29 UTCEG score recompute
  2. 2026-08-30 05:29 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-28 02:52 UTCEG score recompute
  6. 2026-08-28 02:52 UTCGHSA enrichment
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-27 14:02 UTCGHSA enrichment
  9. 2026-08-27 00:15 UTCEG score recompute
  10. 2026-08-27 00:15 UTCGHSA enrichment
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-26 02:25 UTCEG score recompute
  13. 2026-08-26 02:25 UTCGHSA enrichment
  14. 2026-08-25 13:48 UTCEPSS rescore
  15. 2026-08-25 11:01 UTCGHSA enrichment
  16. 2026-08-24 22:11 UTCEG score recompute
  17. 2026-08-24 22:11 UTCGHSA enrichment
  18. 2026-08-24 09:19 UTCGHSA enrichment
  19. 2026-08-23 20:00 UTCGHSA enrichment
  20. 2026-08-23 07:10 UTCGHSA enrichment
  21. 2026-08-22 18:20 UTCGHSA enrichment
  22. 2026-08-22 05:30 UTCEG score recompute
  23. 2026-08-22 05:30 UTCGHSA enrichment
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 16:40 UTCGHSA enrichment
Show 75 more
  1. 2026-08-21 03:40 UTCEG score recompute
  2. 2026-08-21 03:40 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 14:41 UTCGHSA enrichment
  5. 2026-08-20 01:14 UTCEG score recompute
  6. 2026-08-20 01:14 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 09:16 UTCGHSA enrichment
  9. 2026-08-18 20:27 UTCEG score recompute
  10. 2026-08-18 20:27 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 03:43 UTCGHSA enrichment
  13. 2026-08-17 14:18 UTCEG score recompute
  14. 2026-08-17 14:18 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 01:28 UTCEG score recompute
  17. 2026-08-17 01:28 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 12:38 UTCEG score recompute
  20. 2026-08-16 12:38 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 23:48 UTCGHSA enrichment
  23. 2026-08-15 10:58 UTCEG score recompute
  24. 2026-08-15 10:58 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 22:08 UTCGHSA enrichment
  27. 2026-08-14 09:18 UTCEG score recompute
  28. 2026-08-14 09:18 UTCGHSA enrichment
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-13 20:28 UTCGHSA enrichment
  31. 2026-08-13 07:30 UTCGHSA enrichment
  32. 2026-08-12 18:40 UTCEG score recompute
  33. 2026-08-12 18:40 UTCGHSA enrichment
  34. 2026-08-12 13:50 UTCEPSS rescore
  35. 2026-08-12 05:50 UTCGHSA enrichment
  36. 2026-08-11 17:00 UTCEG score recompute
  37. 2026-08-11 17:00 UTCGHSA enrichment
  38. 2026-08-11 13:42 UTCEPSS rescore
  39. 2026-08-11 04:10 UTCEG score recompute
  40. 2026-08-11 04:10 UTCGHSA enrichment
  41. 2026-08-11 00:00 UTCEPSS rescore
  42. 2026-08-10 15:21 UTCGHSA enrichment
  43. 2026-08-10 02:31 UTCEG score recompute
  44. 2026-08-10 02:31 UTCGHSA enrichment
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-09 13:41 UTCGHSA enrichment
  47. 2026-08-09 00:52 UTCGHSA enrichment
  48. 2026-08-08 12:02 UTCGHSA enrichment
  49. 2026-08-07 23:12 UTCEG score recompute
  50. 2026-08-07 23:12 UTCGHSA enrichment
  51. 2026-08-07 10:22 UTCGHSA enrichment
  52. 2026-08-06 21:32 UTCEG score recompute
  53. 2026-08-06 21:32 UTCGHSA enrichment
  54. 2026-08-06 13:46 UTCEPSS rescore
  55. 2026-08-06 08:42 UTCGHSA enrichment
  56. 2026-08-05 19:52 UTCEG score recompute
  57. 2026-08-05 19:52 UTCGHSA enrichment
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-05 07:02 UTCGHSA enrichment
  60. 2026-08-04 18:11 UTCEG score recompute
  61. 2026-08-04 18:11 UTCGHSA enrichment
  62. 2026-08-04 15:10 UTCEPSS rescore
  63. 2026-08-04 10:38 UTCEPSS rescore
  64. 2026-08-04 04:59 UTCGHSA enrichment
  65. 2026-08-03 16:09 UTCEG score recompute
  66. 2026-08-03 16:09 UTCGHSA enrichment
  67. 2026-08-03 10:35 UTCEPSS rescore
  68. 2026-08-03 03:17 UTCGHSA enrichment
  69. 2026-08-02 14:27 UTCEG score recompute
  70. 2026-08-02 14:27 UTCGHSA enrichment
  71. 2026-08-02 02:26 UTCEPSS rescore
  72. 2026-08-02 01:37 UTCGHSA enrichment
  73. 2026-08-01 12:47 UTCEG score recompute
  74. 2026-08-01 12:46 UTCGHSA enrichment
  75. 2026-08-01 04:15 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-22099?
CVE-2026-22099 is a high vulnerability published on July 13, 2026. The charging station does not require authentication for Bluetooth commands to perform actions. The functionality exposed includes sensitive information leakage, triggering reboots, or pushing a firmware update URL.
When was CVE-2026-22099 disclosed?
CVE-2026-22099 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-22099 actively exploited?
CVE-2026-22099 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 77.8% of all scored CVEs.
What is the CVSS score of CVE-2026-22099?
CVE-2026-22099 has a CVSS v4.0 base score of 8.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-22099?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22099, 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-22099

Explore →

Is Your Infrastructure Affected by CVE-2026-22099?

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