CVE-2026-22790
Received Received - Intake
Stack Buffer Overflow in EVerest Enables Remote Code Execution

Publication date: 2026-03-26

Last updated on: 2026-03-31

Assigner: GitHub, Inc.

Description
EVerest is an EV charging software stack. Prior to version 2026.02.0, `HomeplugMessage::setup_payload` trusts `len` after an `assert`; in release builds the check is removed, so oversized SLAC payloads are `memcpy`'d into a ~1497-byte stack buffer, corrupting the stack and enabling remote code execution from network-provided frames. Version 2026.02.0 contains a patch.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-26
Last Modified
2026-03-31
Generated
2026-05-07
AI Q&A
2026-03-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linuxfoundation everest to 2026.02.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-22790 is a high-severity stack overflow vulnerability in the EVerest EV charging software stack, specifically in the function HomeplugMessage::setup_payload.

The vulnerability occurs because the function uses an assert statement to check the length of the SLAC payload, but this check is removed in release builds. Without this check, oversized payloads are copied into a fixed-size stack buffer of about 1497 bytes using memcpy, causing a stack buffer overflow.

This overflow corrupts adjacent memory on the stack and enables remote code execution from network-provided frames, allowing an attacker to run arbitrary code remotely.

The issue affects versions prior to 2026.02.0, which contains a patch to fix this problem.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows remote code execution with high impact on confidentiality, integrity, and availability of the affected system. Such a compromise can lead to unauthorized access to sensitive data and disruption of services.

As a result, organizations using affected versions of the EVerest software may face challenges in maintaining compliance with standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data, ensuring data integrity, and maintaining system availability.

Failure to patch this vulnerability could lead to data breaches or service interruptions, potentially resulting in regulatory penalties or legal consequences.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability arises from a stack buffer overflow in the HomeplugMessage::setup_payload function when processing oversized SLAC payloads. Detection involves monitoring for unusually large SLAC frames exceeding approximately 1497 bytes, which can trigger the overflow.

Since the vulnerability is triggered by network-provided frames with oversized payloads, network traffic analysis tools can be used to detect suspicious SLAC frames.

Suggested commands include using packet capture tools like tcpdump or Wireshark to filter and inspect SLAC frames for payload sizes larger than the expected limit.

  • tcpdump -i <interface> -s 2000 -w capture.pcap 'ether proto 0x88e1' # Capture HomePlug AV frames (SLAC frames use this Ethertype)
  • Use Wireshark to open capture.pcap and filter for SLAC frames with payload length > 1497 bytes.

Additionally, monitoring for crashes or abnormal behavior in the EVerest software, especially in release builds, can indicate exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

The primary mitigation is to upgrade the EVerest software to version 2026.02.0 or later, which contains the patch fixing this vulnerability.

Until the upgrade can be applied, restrict or block adjacent network access to the affected system to prevent attackers from sending malicious SLAC frames.

Implement network-level filtering to drop SLAC frames with payloads larger than the safe limit (~1497 bytes) to prevent exploitation.

Monitor system logs and application behavior for signs of crashes or suspicious activity related to SLAC frame processing.


How can this vulnerability impact me? :

This vulnerability allows an attacker with adjacent network access to execute arbitrary code remotely on the affected system without requiring any privileges or user interaction.

The impact includes severe compromise of confidentiality, integrity, and availability of the system running the vulnerable EVerest software.

  • Remote code execution
  • Stack memory corruption
  • Potential full system compromise

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart