CVE-2026-26290: ev.energy · CWE-613
Affects ev.energySource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 27 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EV Energyev.energy | Affected
| Fixed in– |
GitHubcisagov/ev.energypkg:github/cisagov/ev.energyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-26290, organizations should implement the following specific measures: 1) Enforce unique session identifiers per connection and implement robust session management to prevent multiple simultaneous connections using the same session ID. 2) Introduce cryptographically secure, unpredictable session tokens instead of predictable charging station identifiers to prevent session hijacking. 3) Implement backend validation to detect and block duplicate or conflicting session connections. 4) Rate-limit WebSocket connection attempts to mitigate denial-of-service risks from session flooding. 5) Employ mutual authentication mechanisms between charging stations and backend services to ensure only authorized devices can establish sessions. 6) Monitor WebSocket traffic for anomalous patterns indicative of session hijacking or DoS attempts. 7) Coordinate with EV Energy for official patches or updates once available and apply them promptly. 8) Consider network segmentation and firewall rules to restrict access to backend WebSocket endpoints to trusted sources only. These targeted actions go beyond generic advice by focusing on session management, authentication, and traffic control specific to the ev.energy WebSocket backend architecture.
Description
The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests.