Telemetry disruption via unrestricted WebSocket authentication attempts
Published Feb 27, 2026 · Updated Feb 27, 2026
Improper restriction of authentication attempts in all ev.energy versions allows remote attackers to interrupt charger telemetry. The WebSocket API accepts an unrestricted number of authentication requests because it applies no rate limit, enabling request floods and credential guessing. No credentials or user interaction are required; abuse can suppress or mis-route legitimate telemetry, while brute force can gain unauthorized access.
Summary
What happened
Improper restriction of authentication attempts in all ev.energy versions allows remote attackers to interrupt charger telemetry. The WebSocket API accepts an unrestricted number of authentication requests because it applies no rate limit, enabling request floods and credential guessing. No credentials or user interaction are required; abuse can suppress or mis-route legitimate telemetry, while brute force can gain unauthorized access.
The record
- CVE
- CVE-2026-24445
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- ev.energy
- Product
- ev.energy
- Classifications
- CWE-307, CAPEC-49, T1499.003, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2026CVE publishedPublication date reported by the CVE source.
- Feb 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo