Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27815: CWE-787: Out-of-bounds Write in EVerest everest-core

0
Medium
VulnerabilityCVE-2026-27815cvecve-2026-27815cwe-787
Published: Thu Mar 26 2026 (03/26/2026, 16:30:29 UTC)
Source: CVE Database V5
Vendor/Project: EVerest
Product: everest-core

Description

EVerest is an EV charging software stack. Prior to versions to 2026.02.0, ISO15118_chargerImpl::handle_session_setup copies a variable-length payment_options list into a fixed-size array of length 2 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/26/2026, 17:02:46 UTC

Technical Analysis

CVE-2026-27815 is an out-of-bounds write vulnerability classified under CWE-787 found in the EVerest everest-core software, which is part of an EV charging software stack. The vulnerability arises in the ISO15118_chargerImpl::handle_session_setup function, where a variable-length list of payment_options is copied into a fixed-size array of length 2 without bounds checking. This unsafe copying can lead to memory corruption by writing beyond the allocated buffer. The issue is exacerbated by the fact that schema validation for MQTT command payloads is disabled by default, allowing oversized payloads to be processed unchecked. An attacker who can send malicious MQTT commands to the EVSE (Electric Vehicle Supply Equipment) can exploit this flaw to corrupt adjacent memory, potentially altering EVSE state or causing the charging process to crash. The vulnerability does not require authentication or user interaction but does require access to the MQTT interface, which is typically local or network-restricted. The CVSS 4.0 base score is 5.5 (medium severity), reflecting the local attack vector, no privileges required, no user interaction, and high impact on availability. The flaw was patched in version 2026.02.0 of everest-core. No known exploits have been reported in the wild to date. The vulnerability highlights the risks of disabled schema validation and unsafe memory operations in embedded IoT and EV infrastructure software.

Potential Impact

The impact of CVE-2026-27815 on organizations operating EV charging infrastructure can be significant. Successful exploitation can lead to memory corruption, which may cause the EVSE software to crash or behave unpredictably, resulting in denial of service for EV charging stations. This disruption can affect EV users' ability to charge vehicles, potentially causing operational and reputational damage to charging network operators. In worst cases, corrupted EVSE state could lead to incorrect charging behavior or safety risks, though no such direct safety impact is confirmed. Because the vulnerability requires access to the MQTT interface, attackers with network access to EVSE devices could exploit it to disrupt service. Given the increasing adoption of EVs and charging infrastructure worldwide, widespread exploitation could impact critical transportation and energy sectors. However, the lack of known exploits and the medium severity rating suggest the threat is moderate but should not be underestimated, especially in environments with lax network segmentation or disabled schema validation.

Mitigation Recommendations

To mitigate CVE-2026-27815, organizations should immediately upgrade the everest-core software to version 2026.02.0 or later, which contains the patch fixing the out-of-bounds write. Additionally, enable schema validation for MQTT payloads to prevent oversized or malformed commands from being processed. Network segmentation and strict access controls should be enforced to restrict MQTT interface access only to trusted and authenticated entities, minimizing exposure to potential attackers. Implement monitoring and anomaly detection on MQTT traffic to identify unusual or oversized payloads that could indicate exploitation attempts. Conduct regular security audits and code reviews of embedded software components to detect unsafe memory operations. Finally, maintain an incident response plan for EVSE infrastructure to quickly address potential disruptions caused by exploitation attempts.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-24T02:31:33.268Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69c562cdf4197a8e3be49a81

Added to database: 3/26/2026, 4:46:05 PM

Last enriched: 3/26/2026, 5:02:46 PM

Last updated: 3/26/2026, 8:25:42 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses