EVerest has use-after-free in auth timeout timer via race condition
Summary
| CVE | CVE-2026-27813 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-03-26 17:16:33 UTC |
| Updated | 2026-03-30 20:56:42 UTC |
| Description | EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to use-after-free. This is triggered by EV plug-in/unplug and RFID/RemoteStart/OCPP authorization events (or delayed authorization response). Version 2026.2.0 contains a patch. |
Risk And Classification
Primary CVSS: v3.1 5.3 MEDIUM from [email protected]
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
EPSS: 0.000220000 probability, percentile 0.057870000 (date 2026-04-01)
Problem Types: CWE-416 | CWE-416 CWE-416: Use After Free
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 5.3 | MEDIUM | CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H |
| 3.1 | CNA | DECLARED | 5.3 | MEDIUM | CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H |
CVSS v3.1 Breakdown
Attack Vector
PhysicalAttack Complexity
HighPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
LowIntegrity
LowAvailability
HighCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linuxfoundation | Everest | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | EVerest | Everest-core | affected < 2026.02.0 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/EVerest/EVerest/security/advisories/GHSA-vgmh-mmg3-22m6 | [email protected] | github.com | Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.