VulnerabilityPublished 26 Mar 2026

CVE-2026-33015: everest-core · Incorrect Authorization

Affects everest-coreSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.2 Medium : upgrade to 2026.02.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.2Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2026.02.0

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

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

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

Affected software

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

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

AI-suggested

Organizations should immediately upgrade all EVerest everest-core deployments to version 2026.02.0 or later, where the authorization flaw has been patched. Until upgrades are complete, physical and network access to EVSE devices should be tightly controlled to prevent unauthorized toggling of the EV's BCB. Implement network segmentation and access controls to restrict EVSE management interfaces to trusted personnel and systems only. Monitor EVSE logs and charging session states for anomalous PrepareCharging transitions following RemoteStop commands, which may indicate exploitation attempts. Incorporate multi-factor authentication and role-based access controls in CSMS and EVSE management systems to reduce risk of unauthorized commands. Conduct regular security audits and penetration testing focused on EVSE session management logic. Coordinate with EVSE manufacturers and vendors to ensure timely patch deployment and verify firmware integrity. Finally, update incident response plans to include scenarios involving EV charging session manipulation.

Description

EVerest is an EV charging software stack. Prior to version 2026.02.0, even immediately after CSMS performs a RemoteStop (StopTransaction), the EVSE can return to `PrepareCharging` via the EV's BCB toggle, allowing session restart. This breaks the irreversibility of remote stop and can bypass operational/billing/safety controls. Version 2026.02.0 contains a patch.

Impact

This vulnerability can lead to unauthorized restarting of EV charging sessions after a remote stop command, which can have several negative consequences for organizations operating EV charging infrastructure. Operationally, it undermines the control CSMS has over charging sessions, potentially allowing users or attackers to bypass session termination. This can result in inaccurate billing, as sessions may continue without proper authorization or accounting. From a safety perspective, the ability to restart charging without CSMS approval could lead to unsafe charging conditions or violate regulatory requirements. The integrity of session management is compromised, which may erode trust in the charging infrastructure. While the attack requires local or physical access to the EVSE or EV, the widespread deployment of EV charging stations increases the attack surface. Organizations relying on affected versions risk financial losses, regulatory penalties, and reputational damage if this vulnerability is exploited. The lack of confidentiality impact limits data exposure risks, but the integrity and availability impacts are significant for critical EV charging operations.

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/security/advisories/GHSA-pw9q-2287-cchc (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 17:33 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats