Unauthenticated session hijacking via predictable station identifiers
Published Feb 27, 2026 · Updated Feb 27, 2026
Insufficient session expiration in ev.energy allows remote attackers to hijack charging-station sessions through predictable identifiers. The WebSocket backend accepts concurrent endpoints under one station identifier and assigns commands to the newest connection, displacing the legitimate station. No authentication or user interaction is required; the attacker can receive station commands or interrupt service with valid session requests.
Summary
What happened
Insufficient session expiration in ev.energy allows remote attackers to hijack charging-station sessions through predictable identifiers. The WebSocket backend accepts concurrent endpoints under one station identifier and assigns commands to the newest connection, displacing the legitimate station. No authentication or user interaction is required; the attacker can receive station commands or interrupt service with valid session requests.
The record
- CVE
- CVE-2026-26290
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- ev.energy
- Product
- ev.energy
- Classifications
- CWE-613, T1499, T1078
- 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