dbcve.org
EverestOperating system · Linuxfoundation

CVE-2026-27813

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 2026.02.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

EVerest versions before 2026.02.0 contain a data race condition that leads to use-after-free. The race occurs when EV plug-in/unplug events and authorization events (RFID, RemoteStart, OCPP, or delayed authorization responses) execute concurrently without proper synchronization, causing a memory safety violation when one thread frees a resource while another still references it.

MitigationUpgrade to EVerest version 2026.2.0 or later, which contains the patch addressing the synchronization issue between authorization and plug/unplug state transitions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EverestOperating system
Affected:< 2026.02.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed EVerest version
    Run 'everest --version' or check the version reported by the main everest-core process. Alternatively, inspect the package metadata if installed via package manager.
    Affected if The version is before 2026.02.0 (e.g., 2025.x, 2024.x, or any nightly build earlier than the release date).
  2. Check if authorization modules are active
    Review the EVerest configuration file (usually in /etc/everest or the deployment's config directory) for entries under 'authorization' that enable RFID, RemoteStart, OCPP, or delayed authorization.
    Affected if One or more of these authorization modules are configured and actively processing requests while the system is running.
  3. Verify charging sessions occur with plug/unplug events
    Monitor the system for电动汽车 (EV) charging sessions. Check if the system logs or status shows any plug-in/unplug events occurring during active authorization processing.
    Affected if Charging sessions with physical plug/unplug events have occurred or are expected to occur while authorization is in progress.
  4. Review logs for race condition symptoms
    Search EVerest logs (typically in /var/log/everest/ or stdout from the everest-core service) for indicators of memory safety issues: use-after-free errors, segmentation faults, or unexpected crashes during concurrent plug/unplug and authorization events.
    Affected if Logs contain crashes, memory errors, or race condition warnings occurring during concurrent authorization and plug/unplug operations.

You are affected if your EVerest version is before 2026.02.0 AND you use any authorization method (RFID, RemoteStart, OCPP, or delayed authorization) while handling EV plug/unplug events in a running system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.02.0 or later
Fixed in 2026.02.0
Interim mitigation

Upgrade to EVerest version 2026.2.0 or later, which contains the patch addressing the synchronization issue between authorization and plug/unplug state transitions.

Recommended fix Moderate confidence

2026.02.0

  1. Identify the current EVerest version in use by checking the installed package or build configuration
  2. Review the EVerest release notes for version 2026.02.0 to understand the fix for the use-after-free vulnerability
  3. Plan the upgrade ensuring compatibility with your existing system dependencies
  4. Test the upgrade in a non-production environment to verify the data race issue is resolved
  5. Deploy version 2026.02.0 or later to the production environment
  6. Monitor the system after upgrade for any authorization-related issues or crashes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Everest Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27813 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data