# CVE-2025-68139: Business logic in everest-core

> Attackers can exploit connection handling flaws in EVerest EV charging software by leveraging default settings that fail to terminate sessions on errors.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2026
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-wqh4-pj54-6xv9

## What is CVE-2025-68139?

CVE-2025-68139 is a medium-severity vulnerability in everest-core, published on 21 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EVerest is an EV charging software stack. In all versions up to and including 2025.12.1, the default value for `terminate_connection_on_failed_response` is `False`, which leaves the responsibility for session and connection termination to the EV. In this configuration, any errors encountered by the module are logged but do not trigger countermeasures such as session and connection reset or termination. This could be abused by a malicious user in order to exploit other weaknesses or vulnerabilities. While the default will stay at the setting that is described as potentially problematic in this reported issue, a mitigation is available by changing the `terminate_connection_on_failed_response`  setting to `true`. However this cannot be set to this value by default since it can trigger errors in vehicle ECUs requiring ECU resets and lengthy unavailability in charging for vehicles. The maintainers judge this to be a much more important workaround then short-term unavailability of an EVSE, therefore this setting will stay at the current value.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2025-68139?

It affects 1 product.


Products: Linuxfoundation Everest.

## How do I fix CVE-2025-68139?

No fix has been published for CVE-2025-68139 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-68139 being exploited?

There is no known exploitation of CVE-2025-68139 in the wild and no public exploit code.

## Other vulnerabilities in everest-core

- [CVE-2026-22790](https://insights.sbomify.com/CVE-2026-22790/): EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload (high 8.8)
- [CVE-2026-22593](https://insights.sbomify.com/CVE-2026-22593/): EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing (high 8.4)
- [CVE-2026-23995](https://insights.sbomify.com/CVE-2026-23995/): EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ (high 8.4)
- [CVE-2025-68137](https://insights.sbomify.com/CVE-2025-68137/): EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop (high 8.4)
- [CVE-2026-33009](https://insights.sbomify.com/CVE-2026-33009/): EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68139 and fix it if it is affected.

What it is: CVE-2025-68139 is a medium-severity vulnerability in everest-core, published on 21 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68139 in the wild and no public exploit code.

Affected product: everest-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68139/ (Markdown: https://insights.sbomify.com/CVE-2025-68139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68139
- OSV: https://osv.dev/vulnerability/CVE-2025-68139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68139/
Summaries are generated and may contain mistakes; the official description above is the record.