A vulnerability identified as problematic has been detected in EVerest everest-core 2025.9.0/2025.10.0/2025.12.0 . Impacted is the function Charger::deauthorize . This manipulation causes incorrect authorization. This vulnerability is tracked as CVE-2026-29044 . The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353678 · CVE-2026-29044 · GHSA-GX37-P775-QF5V
EVEREST EVEREST-CORE 2025.9.0/2025.10.0/2025.12.0 CHARGER::DEAUTHORIZE AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.1 $0-$5k 2.17+
Summaryinfo
A vulnerability labeled as problematic has been found in EVerest everest-core. The affected element is the function Charger::deauthorize. Such manipulation leads to authorization. This vulnerability is listed as CVE-2026-29044. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.
Detailsinfo
A vulnerability was found in EVerest everest-core and classified as problematic. Affected by this issue is the function Charger::deauthorize. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. 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. This allows attackers to bypass intended access restrictions. Impacted is integrity, and availability. CVE summarizes:
EVerest is an EV charging software stack. Prior to version 2026.02.0, when WithdrawAuthorization is processed before the TransactionStarted event, AuthHandler determines `transaction_active=false` and only calls `withdraw_authorization_callback`. This path ultimately calls `Charger::deauthorize()`, but no actual stop (StopTransaction) occurs in the Charging state. As a result, authorization withdrawal can be defeated by timing, allowing charging to continue. Version 2026.02.0 contains a patch.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-29044 since 03/03/2026. The exploitation is known to be difficult. The attack may be launched remotely. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but there is no available exploit.
Upgrading to version 2026.02.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-16230).
Productinfo
Vendor
EVerest
Name
everest-core
Version
2025.9.0
2025.10.0
2025.12.0
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.1
VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.0
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: everest-core 2026.02.0
Timelineinfo
03/03/2026 CVE reserved
03/26/2026 +23 days Advisory disclosed
03/26/2026 +0 days VulDB entry created
03/26/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: GHSA-gx37-p775-qf5v
Status: Confirmed
CVE: CVE-2026-29044 (🔒)
GCVE (CVE): GCVE-0-2026-29044
GCVE (VulDB): GCVE-100-353678
EUVD: 🔒
Entryinfo
Created: 03/26/2026 19:00
Updated: 03/26/2026 19:38
Changes: 03/26/2026 19:00 (64), 03/26/2026 19:38 (1)
Complete: 🔍
Cache ID: 99:7F1:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸