CVE-2025-68138VulnerabilityPublished 21 Jan 2026Updated 22 Jan 2026

CVE-2025-68138: everest-core · Unthrottled Resource Allocation

Affects everest-coreSource CVE Database V5

Not known to be exploited · CVSS 4.7 Medium : upgrade to 0.30 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.7Medium

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

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: None
Availability: Low

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 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/libocpp to 0.30.

Affected software

Product	Affected	Fixed in
EVeresteverest-core	Affected =libocpp < 0.30.1	Fixed in–
GitHubeverest/libocpp`pkg:github/everest/libocpp`Other threats	Affected <0.30	Fixed in 0.30

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

AI-suggested

To mitigate this vulnerability, European EV infrastructure operators should immediately upgrade all instances of the EVerest libocpp library to version 0.30.1 or later, where the memory leak is fixed. Operators should audit their software stacks to identify any usage of vulnerable libocpp versions. Implementing runtime monitoring of memory usage on charging stations and backend systems can help detect abnormal memory growth indicative of exploitation attempts. Network segmentation and limiting access to charging station management interfaces can reduce exposure to potential attackers. Additionally, operators should establish incident response procedures to quickly reboot or isolate affected devices if memory exhaustion symptoms appear. Vendors and integrators should verify that their products incorporate the patched library version and communicate updates promptly to customers. Finally, maintaining up-to-date software inventories and vulnerability management processes will help prevent similar issues.

Description

CVE-2025-68138 is a medium severity vulnerability in the EVerest libocpp library, a C++ implementation of the Open Charge Point Protocol used in EV charging software. The flaw involves a memory leak caused by failure to free memory allocated by strdup calls during connection attempts. This can lead to memory exhaustion and denial of service on affected systems running libocpp versions prior to 0.30.1. Exploitation requires network access but no authentication or user interaction. The vulnerability impacts availability but not confidentiality or integrity. No known exploits are reported in the wild yet. The issue is fixed in libocpp version 0.30.

Impact

For European organizations, this vulnerability poses a risk primarily to the availability of EV charging infrastructure. Memory exhaustion leading to denial of service can disrupt charging services, causing operational downtime and customer dissatisfaction. This is especially critical as Europe aggressively promotes EV adoption and relies on robust charging networks. Disruptions could affect public charging stations, fleet operators, and utilities managing EV infrastructure. The impact extends to potential economic losses, reduced trust in EV infrastructure reliability, and cascading effects on smart grid management if charging stations are integrated with grid control systems. Since the vulnerability does not affect confidentiality or integrity, data breaches are unlikely, but service interruptions could have significant operational consequences. Organizations operating or managing EV charging networks must consider this vulnerability in their risk assessments and incident response planning.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (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 29 Jan 2026, 08:40 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats