CVE-2026-29044: everest-core · Incorrect Authorization
Affects everest-coreSource CVE Database V5
Not known to be exploited · CVSS 5.0 Medium : upgrade to 2026.02.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.02.0
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:LExploitation 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.
What to do
Upgrade everest-core and everest/everest-core to 2026.02.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EVeresteverest-core | Affected
| Fixed in
|
GitHubeverest/everest-corepkg:github/everest/everest-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should upgrade all instances of everest-core to version 2026.02.0 or later, which contains the patch addressing this authorization flaw. In addition, operators should implement monitoring and alerting for anomalous WithdrawAuthorization and StopTransaction message sequences to detect potential exploitation attempts. Network segmentation and strict access controls should be enforced to limit which entities can send authorization-related commands, reducing the risk of unauthorized message injection. Conduct thorough testing of authorization workflows after patching to ensure the WithdrawAuthorization and StopTransaction events are correctly synchronized. Consider implementing additional logging and audit trails for transaction state changes to facilitate forensic analysis if suspicious activity is detected. Finally, coordinate with EV charging hardware vendors to verify that firmware and software versions are compatible and secure against this timing-based vulnerability.
Description
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.