CVE-2026-27816
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 · uneditedEVerest is an EV charging software stack. Prior to versions to 2026.02.0, ISO15118_chargerImpl::handle_update_energy_transfer_modes copies a variable-length list into a fixed-size array of length 6 without bounds checking. With schema validation disabled by default, oversized MQTT Cmd payloads can trigger out-of-bounds writes and corrupt adjacent EVSE state or crash the process. Version 2026.02.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 confidenceBuffer overflow vulnerability in EVerest's ISO15118_chargerImpl::handle_update_energy_transfer_modes function where a variable-length list is copied into a fixed-size array of 6 elements without bounds checking. When schema validation is disabled (the default), oversized MQTT command payloads can trigger out-of-bounds writes, corrupting adjacent EVSE state or causing process crashes.
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< 2026.02.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed EVerest versionLocate the EVerest installation and retrieve its version identifier (typically via package manager, docker image tag, or version file in the installation directory)Affected if The installed version is earlier than 2026.02.0 (e.g., 2025.x, 2024.x, or any version number less than 2026.02.0)
-
Verify schema validation configuration for MQTTInspect the EVerest deployment configuration files for MQTT message handling settings, specifically looking for the schema validation toggle or flagAffected if Schema validation is explicitly disabled or set to false (this is the default configuration and makes the vulnerability exploitable)
-
Confirm ISO15118_chargerImpl module is activeCheck the running EVerest configuration or module list to determine if the ISO15118_chargerImpl component is loaded and actively processing messagesAffected if The ISO15118_chargerImpl module is present and operational in the deployment
-
Review MQTT message input handlingExamine MQTT subscriber configuration or message handler setup for the ISO15118_charger to see if there are size limits on incoming payloadsAffected if There are no effective size restrictions on MQTT messages received by the ISO15118 charger (or limits are set higher than 6 elements for the energy transfer mode list)
The environment is affected if running any EVerest version before 2026.02.0 with schema validation disabled (the default) while the ISO15118_chargerImpl module is active and processing MQTT messages without proper payload size constraints.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.02.0
Upgrade to version 2026.02.0 which contains the patch. As a workaround, enable schema validation for MQTT messages if the EVerest deployment configuration allows it.
2026.02.0
- 1. Identify the current EVerest version deployed in your environment.
- 2. Obtain version 2026.02.0 or later from the official EVerest repository (github.com/EVerest/EVerest).
- 3. Follow the standard upgrade procedure for your deployment method (package manager, container, or source build).
- 4. Verify the upgrade was successful by checking the EVerest version after installation.
- 5. Test that ISO15118 charger functionality operates normally with various energy transfer mode requests.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27816 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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