CVE-2025-68132VulnerabilityPublished 21 Jan 2026

CVE-2025-68132: everest-core · Out-of-bounds Read

Affects everest-coreSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low : upgrade to 2025.12.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

2.4Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.12.0

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector: Physical
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack) or persistent.
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade everest-core and everest/everest-core to 2025.12.0.

Affected software

Product	Affected	Fixed in
EVeresteverest-core	Affected <2025.12.0	Fixed in 2025.12.0
GitHubeverest/everest-core`pkg:github/everest/everest-core`Other threats	Affected <2025.12.0	Fixed in 2025.12.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize upgrading EVerest everest-core to version 2025.12.0 or later, where the vulnerability is fixed. In addition, organizations should implement strict physical and logical access controls to the serial interfaces of EV charging equipment to prevent unauthorized manipulation. Monitoring and anomaly detection on serial communication channels can help identify malformed SLIP frames indicative of exploitation attempts. Where immediate patching is not feasible, isolating the affected devices from untrusted networks and restricting serial port access can reduce risk. Vendor coordination for timely updates and incident response planning for potential denial-of-service events are also recommended.

Description

CVE-2025-68132 is an out-of-bounds read vulnerability in the EVerest everest-core EV charging software stack prior to version 2025.12.0. The flaw occurs in the DZG_GSH01 powermeter SLIP parser's is_message_crc_correct function, which reads bytes from a vector without verifying its size, leading to potential memory access violations. An attacker with control over the serial input can send malformed SLIP frames that cause the process to crash due to out-of-bounds reads and pop_back underflow. This vulnerability does not require authentication or user interaction and has a low CVSS score of 2.4, indicating limited impact. The issue is fixed in version 2025.12.0.

Impact

For European organizations operating EV charging infrastructure using EVerest everest-core versions prior to 2025.12.0, this vulnerability poses a risk of service disruption due to process crashes triggered by malformed serial input. Although the impact is limited to availability and does not compromise confidentiality or integrity, denial of service in critical EV charging stations could affect operational continuity and customer experience. In regions with high EV adoption, such disruptions could have cascading effects on transportation and energy management systems. The requirement for attacker control over the serial link limits remote exploitation, but insider threats or compromised local devices could exploit this flaw. Given the increasing reliance on EV infrastructure in Europe, even low-severity vulnerabilities warrant timely remediation to maintain service reliability and trust.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Jan 2026, 20:25 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats