VulnerabilityPublished 21 Jan 2026

CVE-2025-68139: everest-core · Session Fixation

Affects everest-coreSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
EVeresteverest-core	Affected <=2025.12.1	Fixed in–
GitHubeverest/everest-core`pkg:github/everest/everest-core`Other threats	Affected <=2025.12.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European EV charging operators and software integrators using EVerest everest-core should immediately evaluate the feasibility of enabling the terminate_connection_on_failed_response setting to true, understanding that this may cause ECU resets and temporary vehicle charging unavailability. To mitigate operational impact, operators should implement this change during planned maintenance windows and communicate potential disruptions to customers. Additionally, monitoring and anomaly detection should be enhanced around session management events to detect suspicious session fixation attempts or abnormal session behaviors. Operators should also ensure that their EVSE (Electric Vehicle Supply Equipment) firmware and software are updated to the latest versions beyond 2025.12.1 once patches or safer default configurations become available. Network segmentation and strict access controls should be enforced to limit exposure of the EV charging management interfaces to trusted networks only. Finally, collaboration with vehicle manufacturers to better understand ECU reset impacts and explore firmware updates that tolerate stricter session management policies without causing resets could provide a longer-term resolution.

Description

CVE-2025-68139 is a session fixation vulnerability in the EVerest everest-core EV charging software stack affecting versions up to 2025.12.1. The default configuration does not terminate sessions or connections upon failed responses, allowing attackers to potentially exploit session management weaknesses. Although changing the setting to terminate connections on failure mitigates the issue, it is not enabled by default due to risks of causing ECU resets and vehicle charging unavailability. The vulnerability has a medium severity with a CVSS score of 4.3, indicating limited impact on confidentiality and integrity without affecting availability. No known exploits are reported in the wild. European EV charging infrastructure operators using EVerest software should carefully evaluate the trade-offs between security and operational stability. Mitigation involves enabling the terminate_connection_on_failed_response setting while preparing for possible vehicle ECU disruptions.

Impact

For European organizations, particularly those operating EV charging infrastructure or managing fleets of electric vehicles, this vulnerability poses a moderate risk. Exploitation could allow attackers to manipulate session states, potentially enabling unauthorized actions or facilitating further attacks on the EV or charging station systems. While the vulnerability does not directly compromise confidentiality or availability, it undermines session integrity, which could lead to unauthorized charging sessions, billing fraud, or disruption of charging workflows. The operational impact is complicated by the fact that enabling the mitigation setting may cause vehicle ECU resets, leading to temporary unavailability of charging services and customer dissatisfaction. This trade-off could affect service reliability and trust in EV charging networks. Given Europe's strong push towards EV adoption and the critical role of charging infrastructure, any disruption or security compromise could have cascading effects on transportation and energy sectors. Additionally, attackers might leverage this vulnerability as a foothold for more sophisticated attacks targeting connected vehicle systems or grid management components.

CWE-384Session Fixation (opens in a new tab)
Compound weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
Architecture and Design
Invalidate any existing session identifiers prior to authorizing a new user session.
Architecture and Design
For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value.
Operation · Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
OWASP Cheat Sheets
Session Management (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Forging (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/EVerest/everest-core/security/advisories/GHSA-wqh4-pj54-6xv9 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jan 2026, 08:45 UTC

WeaknessesCWE-384

Technical details

References

Community reviews

Related threats