Session persistence via nonterminating failed V2G responses
Published Jan 21, 2026 · Updated Jan 21, 2026
Session fixation in EVerest Core 2025.12.1 and earlier allows physically proximate attackers to preserve failed V2G sessions. The terminate_connection_on_failed_response setting defaults to false, so failed response codes are logged without resetting or terminating the V2G connection. Access to the charging interface is required, and the retained session is only a stepping stone for exploiting another weakness; no standalone data access or service interruption is reported.
Summary
What happened
Session fixation in EVerest Core 2025.12.1 and earlier allows physically proximate attackers to preserve failed V2G sessions. The terminate_connection_on_failed_response setting defaults to false, so failed response codes are logged without resetting or terminating the V2G connection. Access to the charging interface is required, and the retained session is only a stepping stone for exploiting another weakness; no standalone data access or service interruption is reported.
The record
- CVE
- CVE-2025-68139
- Published
- Jan 21, 2026
- Updated
- Jan 21, 2026
- Vendor
- EVerest
- Product
- EVerest Core
- Classifications
- CWE-384
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2026CVE publishedPublication date reported by the CVE source.
- Jan 21, 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=<= 2025.12.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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