CVE-2026-27828
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 version 2026.02.0, ISO15118_chargerImpl::handle_session_setup uses v2g_ctx after it has been freed when ISO15118 initialization fails (e.g., no IPv6 link-local address). The EVSE process can be crashed remotely by an attacker with MQTT access who issues a session_setup command while v2g_ctx has been released. 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 confidenceThis is a use-after-free vulnerability in EVerest's ISO15118_chargerImpl::handle_session_setup function. When ISO15118 initialization fails (e.g., due to missing IPv6 link-local address), the v2g_ctx structure is freed but the code continues to use it, leading to a crash. An attacker with MQTT access can trigger this by issuing a session_setup command during the failure window.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 EVerest versionCheck the installed EVerest version using package manager, docker image tag, or version file (e.g., 'everest --version' or inspect container metadata)Affected if Version is less than 2026.02.0
-
Verify ISO15118 module is enabledInspect EVerest configuration files or running processes to confirm the ISO15118_chargerImpl module is loaded and activeAffected if ISO15118 charger implementation is enabled and processing session_setup commands
-
Assess MQTT accessibilityReview MQTT broker configuration and network exposure settings to determine if the interface is accessible beyond trusted personnelAffected if MQTT is exposed to untrusted network segments or lacks proper access controls
-
Check IPv6 link-local address availabilityVerify IPv6 is configured on the network interface used by EVerest (e.g., 'ip -6 addr show' or check interface status)Affected if IPv6 link-local address is missing, which can trigger the initialization failure condition that leads to the use-after-free
A system is affected if it runs EVerest versions prior to 2026.02.0 with the ISO15118 module enabled, has MQTT accessible to untrusted actors, and exhibits the IPv6 initialization failure condition that triggers the vulnerability window.
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 EVerest version 2026.02.0 or later, which contains the patch for this use-after-free vulnerability. If upgrading is not immediately feasible, restrict MQTT access to trusted personnel to reduce attack surface.
2026.02.0
- 1. Identify the current installed version of Everest (EVerest) in your environment
- 2. Upgrade the EVerest installation to version 2026.02.0 or later
- 3. After upgrading, verify that ISO15118 initialization completes successfully before processing session_setup commands
- 4. Restart the EVSE process to ensure the patched code is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27828 — 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-27828 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