Executive Summary

This vulnerability exists in the EVerest EV charging software stack, specifically in the everest-core package before version 2026.02.0. It occurs when a WithdrawAuthorization event is processed before the TransactionStarted event during an EV charging session.

In this scenario, the software incorrectly sets the transaction as inactive and only calls a withdraw authorization callback without stopping the charging session. The Charger calls a deauthorize method that does not actually stop the charging if the charger is already in the Charging state.

As a result, charging can continue even after authorization has been withdrawn, due to a timing issue in event handling. This flaw allows unauthorized charging to proceed.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can impact you by allowing charging sessions to continue even after authorization has been withdrawn, effectively bypassing the intended control mechanisms.

This means unauthorized charging can occur, which compromises the integrity of the billing process and may lead to financial losses or disputes.

The vulnerability requires high privileges and has a high attack complexity, but no user interaction is needed. It affects the integrity of the system and has a low impact on availability.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by reproducing the timing condition where a WithdrawAuthorization event is processed before a TransactionStarted event in the EVerest EV charging software stack.

A proof-of-concept test named AuthTest.WithdrawAuthorizationBeforeTransactionStartedBugRepro demonstrates this behavior by simulating the WithdrawAuthorization before TransactionStarted, confirming that withdraw_authorization_callback is called once, stop_transaction_callback is never called, and charging continues despite authorization withdrawal.

While specific commands are not provided, detection would involve monitoring or logging the sequence of these events (WithdrawAuthorization and TransactionStarted) and verifying whether stop_transaction_callback is triggered appropriately.

Useful 0 Not Useful 0

Mitigation Strategies

The immediate mitigation step is to upgrade the EVerest EV charging software stack to version 2026.02.0 or later, where this vulnerability has been patched.

Until the upgrade is applied, carefully monitor charging sessions for irregularities where charging continues despite authorization withdrawal, and consider implementing additional manual or automated checks to ensure that charging stops appropriately when authorization is withdrawn.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability allows unauthorized charging to continue despite authorization withdrawal, which undermines the integrity of the charging and billing process.

While the CVE description and resources do not explicitly mention compliance with standards such as GDPR or HIPAA, the integrity impact could potentially affect regulatory compliance related to billing accuracy and fraud prevention.

There is no direct information provided about impacts on data privacy regulations like GDPR or healthcare regulations like HIPAA.

Useful 0 Not Useful 0