CVE-2026-24445
7.5EV Energy · ev.energy
The WebSocket API in ev.energy lacks authentication rate limiting, which may allow attackers to perform brute-force attacks or disrupt charger telemetry services.
Executive summary
A critical lack of rate limiting in the ev.energy WebSocket API exposes systems to potential unauthorized access via brute-force and service disruption.
Vulnerability
The vulnerability is a lack of rate limiting (CWE-307) within the WebSocket API, which allows unauthenticated attackers to send an unlimited volume of authentication requests.
Business impact
The absence of request restrictions presents a significant risk to operational integrity and account security. An attacker could successfully execute brute-force attacks to gain unauthorized access to user accounts or trigger a denial-of-service condition that suppresses critical charger telemetry. With a CVSS score of 7.5, this vulnerability is classified as High, reflecting the potential for significant disruption to service availability and account compromise.
Remediation
Immediate Action: Contact the vendor immediately to obtain the latest security updates or configuration guidance, as no specific patch version is currently identified.
Proactive Monitoring: Review application access logs for high volumes of authentication requests or repeated failed login attempts originating from single sources.
Compensating Controls: Implement rate limiting at the network edge or via a Web Application Firewall (WAF) to restrict the frequency of incoming WebSocket authentication requests.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Organizations utilizing ev.energy should prioritize the implementation of external traffic filtering to mitigate the risk of brute-force and denial-of-service attacks. Given the lack of a documented patch, monitoring infrastructure and applying WAF-based rate limiting is essential to defend against this vulnerability until the vendor provides a permanent software fix.
Sources
Originally found and disclosed by Khaled Sarieddine and Mohammad Ali Sayed reported this vulnerability to CISA., per the CVE Program record.