CVE-2026-24003VulnerabilityPublished 26 Jan 2026

CVE-2026-24003: everest-core · Improper Authentication

Affects everest-coreSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% 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 26 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-26.

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

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 organizations should implement strict network segmentation to isolate EV charging infrastructure and MQTT servers from untrusted networks, minimizing exposure to remote attackers. Deploy deep packet inspection and anomaly detection on MQTT traffic to identify and block malformed or unauthorized ISO 15118-2 messages that attempt to bypass authentication. Enforce strong access controls and authentication on MQTT brokers to prevent unauthorized publishing of messages. Monitor logs and charging state transitions for unusual patterns indicative of attempted exploitation. Collaborate with EVerest vendors to prioritize patch development and apply updates promptly once available. Consider deploying additional application-layer authentication or message integrity verification mechanisms at the MQTT communication layer to supplement the existing authorization module. Finally, conduct regular security assessments of EV charging infrastructure and related communication protocols to identify and remediate emerging threats.

Description

CVE-2026-24003 is a medium-severity improper authentication vulnerability in the EVerest everest-core EV charging software stack versions up to 2025.12.1. The flaw allows an attacker to bypass sequence state verification and authentication checks via ISO 15118-2 messages published to the MQTT server, enabling transitions to forbidden states and illegitimate context updates. Although the internal state machine prevents leaving the WaitingForAuthentication state without proper authentication, crafted messages can trick the system into preparing to charge and send current. However, the final step of closing contactors to actually deliver current appears not possible without proper state transition. No patches are available at the time of publication, and no known exploits exist in the wild. The vulnerability impacts the integrity of the charging process but does not affect confidentiality or availability. European organizations operating EV charging infrastructure using EVerest software are at risk, especially in countries with high EV adoption and infrastructure deployment. Mitigation involves strict network segmentation, monitoring MQTT traffic for anomalous ISO 15118-2 messages, and applying vendor updates once available.

Impact

For European organizations, this vulnerability poses a risk to the integrity of EV charging operations, potentially allowing unauthorized manipulation of charging states and preparation to deliver current. While the inability to close contactors without proper authentication limits the risk of actual unauthorized power delivery, attackers could still disrupt charging workflows or cause billing inaccuracies. This could undermine trust in EV infrastructure, lead to financial losses, and complicate operational management. Given the increasing adoption of electric vehicles and expansion of charging infrastructure across Europe, especially in countries with aggressive EV policies, the vulnerability could affect charging station operators, utilities, and service providers. Additionally, attackers exploiting this flaw might use it as a foothold for further attacks on connected infrastructure, especially where MQTT servers are exposed or insufficiently secured. The lack of patches increases exposure time, necessitating immediate compensating controls.

Summary

CVE-2026-24003 is an improper authentication vulnerability (CWE-287) in the everest-core component of the EVerest EV charging software stack, affecting versions up to and including 2025.12.1. The vulnerability arises from the ability to bypass sequence state verification and authentication mechanisms within the EVSEManager Charger internal state machine. Normally, authorization is handled by a separate module, and the state machine prevents transitioning out of the WaitingForAuthentication state via ISO 15118-2 communication, which is a protocol standard for EV charging communication. However, due to the modular design and the way ISO 15118-2 messages are published to the MQTT server, an attacker can send crafted messages that cause the system to prepare for charging and even prepare to send current without proper authentication. This means the internal context can be updated with illegitimate data, potentially leading to unauthorized charging operations. The final step to actually send current requires closing contactors, which the attacker cannot trigger without leaving the WaitingForAuthentication state, thus limiting the exploitability. No patches or fixed versions are available at the time of disclosure, and no known exploits have been reported in the wild. The CVSS v3.1 score is 4.3 (medium), reflecting the limited impact on integrity without affecting confidentiality or availability, and the requirement for network access but no privileges or user interaction.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Feb 2026, 08:36 UTC

WeaknessesCWE-287, CWE-863

Technical details

References

Community reviews

Related threats