CVE-2025-68140VulnerabilityPublished 21 Jan 2026

CVE-2025-68140: everest-core · Incorrect Authorization

Affects everest-coreSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2025.9.0 when convenient.

Data as of 25 Oct 2026, 19:02 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 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.9.0

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 2026-10-25.

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 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

Upgrade everest-core and everest/everest-core to 2025.9.0.

Affected software

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

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

AI-suggested

1. Upgrade all affected EVerest everest-core installations to version 2025.9.0 or later, which contains the fix for this vulnerability. 2. Implement strict network segmentation and access controls to restrict access to MQTT brokers and V2G message handlers only to authorized systems and users. 3. Employ network-level authentication and encryption for MQTT communications to prevent unauthorized message injection. 4. Monitor MQTT traffic and V2G session updates for anomalous patterns that could indicate exploitation attempts, such as unexpected session ID 0 messages. 5. Conduct regular security audits and penetration testing focused on EV charging infrastructure to identify and remediate similar authorization weaknesses. 6. Establish incident response procedures specific to EV charging systems to quickly detect and respond to unauthorized session manipulations. 7. Collaborate with EV charging software vendors and industry groups to stay informed about emerging threats and patches.

Description

CVE-2025-68140 is a medium severity authorization vulnerability in the EVerest everest-core EV charging software stack versions prior to 2025.9.0. The flaw arises because when no session is registered, the default session ID is zero, allowing an attacker to submit messages with session ID 0 and bypass authorization checks. This enables unauthorized and anonymous indirect emission of MQTT messages and interaction with V2G message handlers, potentially updating session contexts without proper permissions. The vulnerability does not impact confidentiality or availability but can affect the integrity of session management. Exploitation requires network access but no authentication or user interaction. The issue is fixed in version 2025.9.0.

Impact

For European organizations operating EV charging infrastructure that relies on the EVerest everest-core software stack, this vulnerability poses a risk of unauthorized manipulation of charging sessions. Attackers could inject unauthorized MQTT messages or interact with V2G message handlers, potentially causing incorrect session updates or charging behaviors. While the vulnerability does not directly compromise confidentiality or availability, the integrity of session management is at risk, which could lead to billing inaccuracies, unauthorized energy usage, or disruption of charging operations. Given the increasing adoption of EVs and smart charging infrastructure across Europe, exploitation could undermine trust in EV charging services and cause operational challenges. The impact is more pronounced in environments where network segmentation is weak or where MQTT and V2G communication channels are exposed or insufficiently protected. Since no authentication is required, attackers with network access to the EV charging management systems could exploit this flaw, increasing the threat surface. However, the lack of known exploits in the wild suggests limited active exploitation currently.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/EVerest/everest-core/security/advisories/GHSA-w385-3jwp-x47x (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-863

Technical details

References

Community reviews

Related threats