EVerest: OCPP 1.6 heap corruption caused by lock-free insertion in event_queue
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started). This results in a TSAN data race report and an ASAN/UBSAN misaligned address runtime error being observed. Version 2026.02.0 contains a patch.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-26073
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 03:57 UTC · Revision 1
Source evidence
EVerest: OCPP 1.6 heap corruption caused by lock-free insertion in event_queue
core-osv · Original sourcePublished 26 Mar 2026, 16:15 UTC
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started). This results in a TSAN data race report and an ASAN/UBSAN misaligned address runtime error being observed. Version 2026.02.0 contains a patch.
osv:CVE-2026-26073
Complete source record
{
"id": "ef09a1b1ec41c5645350b19397da19865bb659e76e181a1f6dbb068c32b2e648",
"url": "https://osv.dev/vulnerability/CVE-2026-26073",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "EVerest: OCPP 1.6 heap corruption caused by lock-free insertion in event_queue",
"summary": "EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started). This results in a TSAN data race report and an ASAN/UBSAN misaligned address runtime error being observed. Version 2026.02.0 contains a patch.",
"evidence": "osv:CVE-2026-26073",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-26073",
"aliases": [
"CVE-2026-26073",
"GHSA-jf36-f4f9-7qc2"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/everest/everest",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "b666184ef94a70008388cdec7ec41c14549e9bad"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "2026.02.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
}
],
"versions": [
"2026.02.0-rc4",
"2026.02.0-rc3",
"2026.02.0-rc2",
"2026.02.0-rc1",
"2025.12.1",
"2025.12.0",
"2025.10.0",
"2025.8.0",
"2025.9.0",
"2025.7.0",
"2025.7.0-rc1",
"2025.6.0",
"2025.5.0",
"2025.4.0-rc1",
"2025.3.0",
"2025.2.0",
"2025.1.0-rc2",
"2025.1.0-rc1",
"2024.11.0",
"2024.10.0",
"2024.9.0-rc1",
"2024.8.0",
"2024.7.1",
"2024.7.0",
"2024.6.0-rc2",
"2024.6.0-rc1",
"2024.5.0",
"2024.4.0",
"2024.3.0-rc1",
"2024.2.0",
"2024.1.0",
"2023.12.0",
"2023.10.0",
"2023.9.1",
"2023.9.0",
"2023.8.0",
"2023.7.0",
"2023.6.0",
"2023.5.0",
"2023.3.0",
"2023.2.1",
"2023.2.0",
"2023.1.0",
"2022.12.1",
"2022.12.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-26073.json"
}
}
],
"modified": "2026-10-28T02:30:49.613792932Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/26xxx/CVE-2026-26073.json",
"https://github.com/EVerest/EVerest/security/advisories/GHSA-jf36-f4f9-7qc2",
"https://nvd.nist.gov/vuln/detail/CVE-2026-26073"
],
"provider_metadata": {
"cwe_ids": [
"CWE-122"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/26xxx/CVE-2026-26073.json"
}
},
"related_cves": [
{
"value": "CVE-2026-26073",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517939,
"published_at": "2026-03-26T16:15:22.789+00:00"
}