CVE-2025-68137Public exploit

Service hang or stack corruption via length underflow

Published Jan 21, 2026 · Updated Jan 21, 2026

Integer overflow in EVerest Core before 2025.10.0 allows physically proximate attackers to hang its server or overwrite stack memory. SdpPacket::parse_header() adds the eight-byte header size in 32-bit arithmetic; a near-maximum payload length wraps below the eight bytes already read, and the subtraction becomes a size_t value near SIZE_MAX. Unauthenticated access to the adjacent ISO 15118 IPv6 charging link is required; plaintext handling loops indefinitely, while TLS handling writes beyond the 2,048-byte packet buffer and can alter control flow.

CVSS severity8.3
High
EPSS probability0.97%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Integer overflow in EVerest Core before 2025.10.0 allows physically proximate attackers to hang its server or overwrite stack memory. SdpPacket::parse_header() adds the eight-byte header size in 32-bit arithmetic; a near-maximum payload length wraps below the eight bytes already read, and the subtraction becomes a size_t value near SIZE_MAX. Unauthenticated access to the adjacent ISO 15118 IPv6 charging link is required; plaintext handling loops indefinitely, while TLS handling writes beyond the 2,048-byte packet buffer and can alter control flow.

The record

CVE
CVE-2025-68137
Published
Jan 21, 2026
Updated
Jan 21, 2026
Vendor
EVerest
Product
EVerest Core
Classifications
CWE-835, CWE-120
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 21, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 21, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2025.10.0

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

EVerest · EVerest Coreversion=< 2025.10.0

Published CVSS scores

8.3GitHub, Inc.CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-835Loop with Unreachable Exit Condition ('Infinite Loop')
CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo