CVE-2026-23995: CWE-121: Stack-based Buffer Overflow in EVerest everest-core
EVerest is an EV charging software stack. Prior to version 2026.02.0, stack-based buffer overflow in CAN interface initialization: passing an interface name longer than IFNAMSIZ (16) to CAN open routines overflows `ifreq.ifr_name`, corrupting adjacent stack data and enabling potential code execution. A malicious or misconfigured interface name can trigger this before any privilege checks. Version 2026.02.0 contains a patch.
AI Analysis
Technical Summary
CVE-2026-23995 is a stack-based buffer overflow vulnerability identified in the EVerest everest-core software, a critical component of the EVerest EV charging software stack. The vulnerability arises during the initialization of the CAN (Controller Area Network) interface when the software accepts an interface name longer than IFNAMSIZ (16 bytes). The interface name is stored in the ifreq.ifr_name field, which is a fixed-size buffer. Passing an overly long interface name causes a buffer overflow that overwrites adjacent stack memory, potentially corrupting control data such as return addresses or function pointers. This memory corruption can be exploited to achieve arbitrary code execution. Notably, the vulnerability can be triggered before any privilege checks, meaning that an attacker with local access can exploit it without elevated permissions or user interaction. The flaw affects all versions of everest-core prior to 2026.02.0, which includes a patch that properly bounds the interface name length to prevent overflow. The vulnerability is classified under CWE-121 (Stack-based Buffer Overflow) and has a CVSS v3.1 base score of 8.4, reflecting its high severity. Although no public exploits have been reported yet, the nature of the vulnerability and its potential for code execution make it a critical risk for EV charging infrastructure relying on this software stack.
Potential Impact
The impact of CVE-2026-23995 is significant for organizations deploying the EVerest everest-core software in EV charging stations and related infrastructure. Successful exploitation can lead to arbitrary code execution on the affected system, compromising confidentiality, integrity, and availability. Attackers could execute malicious code to disrupt charging operations, manipulate charging data, or pivot to other networked systems, potentially causing widespread operational disruption. Since the vulnerability can be triggered without privileges or user interaction, it lowers the barrier for attackers with local access, such as insiders or attackers who have gained limited foothold. Given the growing deployment of EV charging infrastructure globally, this vulnerability poses risks to critical energy and transportation sectors. The lack of known exploits in the wild currently reduces immediate risk, but the high severity and ease of exploitation mean that attackers may develop exploits rapidly if the vulnerability becomes widely known.
Mitigation Recommendations
To mitigate CVE-2026-23995, organizations should immediately upgrade all instances of the EVerest everest-core software to version 2026.02.0 or later, which contains the official patch addressing the buffer overflow. Until patching is possible, restrict local access to systems running everest-core to trusted personnel only, and monitor for any unusual interface configuration attempts that might exploit the vulnerability. Implement strict input validation and sanitization on interface names if customization or extension of the software is performed. Employ runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) where supported to reduce exploitation success. Regularly audit and monitor logs for anomalous CAN interface initialization activities. Coordinate with EV infrastructure vendors to ensure timely updates and share threat intelligence related to this vulnerability. Finally, consider network segmentation to isolate EV charging systems from broader enterprise networks to limit lateral movement in case of compromise.
Affected Countries
United States, Germany, China, Japan, South Korea, France, United Kingdom, Netherlands, Canada, Australia
CVE-2026-23995: CWE-121: Stack-based Buffer Overflow in EVerest everest-core
Description
EVerest is an EV charging software stack. Prior to version 2026.02.0, stack-based buffer overflow in CAN interface initialization: passing an interface name longer than IFNAMSIZ (16) to CAN open routines overflows `ifreq.ifr_name`, corrupting adjacent stack data and enabling potential code execution. A malicious or misconfigured interface name can trigger this before any privilege checks. Version 2026.02.0 contains a patch.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-23995 is a stack-based buffer overflow vulnerability identified in the EVerest everest-core software, a critical component of the EVerest EV charging software stack. The vulnerability arises during the initialization of the CAN (Controller Area Network) interface when the software accepts an interface name longer than IFNAMSIZ (16 bytes). The interface name is stored in the ifreq.ifr_name field, which is a fixed-size buffer. Passing an overly long interface name causes a buffer overflow that overwrites adjacent stack memory, potentially corrupting control data such as return addresses or function pointers. This memory corruption can be exploited to achieve arbitrary code execution. Notably, the vulnerability can be triggered before any privilege checks, meaning that an attacker with local access can exploit it without elevated permissions or user interaction. The flaw affects all versions of everest-core prior to 2026.02.0, which includes a patch that properly bounds the interface name length to prevent overflow. The vulnerability is classified under CWE-121 (Stack-based Buffer Overflow) and has a CVSS v3.1 base score of 8.4, reflecting its high severity. Although no public exploits have been reported yet, the nature of the vulnerability and its potential for code execution make it a critical risk for EV charging infrastructure relying on this software stack.
Potential Impact
The impact of CVE-2026-23995 is significant for organizations deploying the EVerest everest-core software in EV charging stations and related infrastructure. Successful exploitation can lead to arbitrary code execution on the affected system, compromising confidentiality, integrity, and availability. Attackers could execute malicious code to disrupt charging operations, manipulate charging data, or pivot to other networked systems, potentially causing widespread operational disruption. Since the vulnerability can be triggered without privileges or user interaction, it lowers the barrier for attackers with local access, such as insiders or attackers who have gained limited foothold. Given the growing deployment of EV charging infrastructure globally, this vulnerability poses risks to critical energy and transportation sectors. The lack of known exploits in the wild currently reduces immediate risk, but the high severity and ease of exploitation mean that attackers may develop exploits rapidly if the vulnerability becomes widely known.
Mitigation Recommendations
To mitigate CVE-2026-23995, organizations should immediately upgrade all instances of the EVerest everest-core software to version 2026.02.0 or later, which contains the official patch addressing the buffer overflow. Until patching is possible, restrict local access to systems running everest-core to trusted personnel only, and monitor for any unusual interface configuration attempts that might exploit the vulnerability. Implement strict input validation and sanitization on interface names if customization or extension of the software is performed. Employ runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) where supported to reduce exploitation success. Regularly audit and monitor logs for anomalous CAN interface initialization activities. Coordinate with EV infrastructure vendors to ensure timely updates and share threat intelligence related to this vulnerability. Finally, consider network segmentation to isolate EV charging systems from broader enterprise networks to limit lateral movement in case of compromise.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-19T18:49:20.658Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c57a7d3c064ed76f9f9cfe
Added to database: 3/26/2026, 6:27:09 PM
Last enriched: 3/26/2026, 6:28:43 PM
Last updated: 3/27/2026, 5:25:34 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.