CVE-2026-29044 json
EVerest: Charging Continues When WithdrawAuthorization Is Processed Before TransactionStarted
published 7mo ago modified 4mo ago also EUVD-2026-16230
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- linuxfoundation everest 2026.02.0
- linuxfoundation libocpp 2026.02.0
Is CVE-2026-29044 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/EVerest/EVerest/security/advisories/GHSA-gx37-p775-qf5v referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:L |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L |
Affected products
- EVerest everest-core
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/EVerest/EVerest/security/advisories/GHSA-gx37-p775-qf5v
exploit, vendor-advisory
Sources
- CVE List CVE-2026-29044
- NVD CVE-2026-29044
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.