LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26290: EV Energy ev.energy Insufficient Session Expiration

The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-26290 affects EV Energy’s ev.energy platform. The backend can accept multiple WebSocket connections using the same charging station session identifier. An attacker may impersonate or shadow a station connection, receive commands meant for it, or disrupt service by crowding the backend with valid-looking session requests.

Executive priority

Treat as a high-priority operational technology/cloud service risk. The main business concern is unauthorized control-path visibility or disruption of EV charging sessions. Prioritize vendor confirmation, exposure review, and monitoring while awaiting or applying official guidance.

Technical view

The issue is CWE-613, insufficient session expiration/session handling. The CVE describes predictable session identifiers tied to charging station identifiers and no effective prevention of duplicate endpoint use. CVSS 3.1 is 7.3, network exploitable, low complexity, no privileges or user interaction required, with limited confidentiality, integrity, and availability impact.

Likely exposure

Organizations using EV Energy ev.energy, listed as affected for “All versions” in the provided CVE data, should assess exposure. The relevant surface is the WebSocket backend used for charging station session association. No CPEs or deployment-specific exposure details were provided.

Exploitation context

The provided sources do not indicate known active exploitation, and the CVE is not listed as CISA KEV. The described attack does not require credentials and relies on predictable or reusable session identifiers. Impact could include station session hijacking, command misdirection, or denial of service.

Researcher notes

Evidence supports a session uniqueness and expiration weakness, not a published exploit. Avoid production testing without authorization. Key validation areas are session identifier predictability, duplicate connection handling, and whether the newest WebSocket connection supersedes the legitimate station session.

Mitigation direction

  • Check EV Energy and CISA advisory guidance for official remediation or compensating controls.
  • Inventory ev.energy-connected charging stations and backend integrations.
  • Reduce unnecessary network exposure to charging session services where feasible.
  • Monitor for duplicate station sessions or unexpected connection displacement events.
  • Escalate to EV Energy support for patch, configuration, or service-side remediation status.

Validation and detection

  • Confirm whether your environment uses EV Energy ev.energy charging session WebSockets.
  • Review logs for multiple endpoints using the same station/session identifier.
  • Check for recent legitimate station disconnects followed by unexpected replacement connections.
  • Verify vendor guidance against your deployed service configuration.
  • Track CISA advisory ICSA-26-057-07 for updates.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-613: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26290 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2026-26290Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EV Energyev.energyAll versionsunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.