CVE-2025-59398: EVerest libocpp · Missing Report of Error Condition
Affects EVerest libocppSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2025
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EVerest libocpp | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Upgrade libocpp to version 0.26.2 or later, where this issue is addressed. 2) Implement input validation and size checks on JSON payloads before processing to ensure they do not exceed expected limits, thereby preventing exceptions from being thrown. 3) Enhance error handling in the OCPP implementation to gracefully manage exceptions caused by oversized inputs, avoiding service crashes. 4) Deploy network-level protections such as firewalls or intrusion detection systems configured to detect and block anomalous or oversized JSON payloads targeting OCPP endpoints. 5) Monitor logs and application behavior for signs of repeated crashes or malformed input attempts, enabling early detection of exploitation attempts. 6) Where possible, restrict network access to OCPP services to trusted sources to reduce exposure to malicious inputs. These steps go beyond generic advice by focusing on proactive input validation, robust error handling, and network-level controls tailored to the OCPP protocol context.
Description
The OCPP implementation in libocpp before 0.26.2 allows a denial of service (EVerest crash) via JSON input larger than 255 characters, because a CiString<255> object is created with StringTooLarge set to Throw.
References
- github.com/EVerest/everest-core/issues/1152 (opens in a new tab)
- github.com/EVerest/everest-core/commit/253432ae7458ad0445f68f9d716086090c2be49c (opens in a new tab)
- github.com/EVerest/libocpp/compare/v0.26.1...v0.26.2 (opens in a new tab)
- github.com/EVerest/libocpp/commit/fb391b4ff16a0a07150e5a8eebf0856fb6623cbe (opens in a new tab)
- github.com/EVerest/libocpp/pull/1052 (opens in a new tab)