Skip to main content

Evoke CSMS CVE-2026-54479

| EUVDEUVD-2026-39566 MEDIUM
Insufficient Session Expiration (CWE-613)
2026-06-25 icscert GHSA-79m4-gx9c-j55f
6.9
CVSS 4.0 · Vendor: icscert
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed CSMS WebSocket endpoint
  2. Delivery
    Guess valid charging-station session ID
  3. Exploit
    Reuse/duplicate predictable session identifier
  4. Execution
    Impersonate station or flood backend
  5. Impact
    Unauthorized access or denial of service

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V7 - Session Management Session expiration enforcement
Exploitation Conditions

Exploitation requires network reachability to the Evoke CSMS WebSocket/OCPP backend and knowledge or guessing of a valid charging-station identifier - which is feasible because the description states session identifiers are predictable and the backend permits multiple endpoints to connect with the same session identifier. Per the CVSS vector (PR:N/UI:N/AC:L) no authentication or user interaction is needed and complexity is low. The principal limiting factor is exposure: if the CSMS endpoint is not internet-reachable (deployed behind VPN/mTLS/IP allow-listing) the attacker must first gain access to the charging network, and impersonation is bounded to stations whose identifiers can be discovered or guessed.

Impact

The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L, base 7.3 High) indicates a network-reachable, low-complexity, unauthenticated attack with low impact across confidentiality, integrity, and availability - consistent with session impersonation plus a DoS path. No EPSS score, KEV listing, POC, or SSVC decision data was supplied, so exploitation probability and automatability cannot be quantified from the input. Practically, the dual impact (impersonate another station/user OR overwhelm the backend) and the unauthenticated network vector make this a genuine priority for any operator running internet-exposed Evoke CSMS endpoints, but the modest per-incident impact (Low C/I/A - not full account takeover or RCE) tempers it below a critical emergency. One caveat: CWE-613 describes session expiration while the description emphasizes predictable/duplicate session identifiers - the underlying weakness is best read as broad session-management failure; confirm exact behavior with the vendor.

Exploit ScenarioDerived

An attacker enumerates or guesses a target charging station's identifier and opens a WebSocket connection to the internet-exposed Evoke CSMS, binding the same predictable session identifier to impersonate that station/user without credentials. Alternatively, the attacker scripts a flood of valid-looking session requests to exhaust backend resources and deny service to legitimate charge points. No public POC is identified, but the low attack complexity and absence of authentication make exploitation straightforward for a motivated actor.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 25, 2026

Authentication bypass and denial-of-service in Evoke Systems' Evoke CSMS electric-vehicle charging station management system stems from predictable WebSocket session identifiers derived from charging station IDs, with no enforcement against duplicate session reuse. Remote unauthenticated attackers can guess or reuse a session identifier to impersonate another charging station/user, or flood the backend with valid session requests to exhaust resources. Reported to CISA by ICS-CERT (advisory ICSA-26-176-02); no public exploit identified at time of analysis and the issue is not listed in CISA KEV.

RemediationAI

No vendor-released patch version is identified in the available data; consult the CISA advisory at https://www.cisa.gov/news-events/ics-advisories/icsa-26-176-02 and contact Evoke Systems directly via https://evokesystems.com/contact-us/ for an updated/fixed release and apply it once published. As compensating controls, do not expose the CSMS WebSocket endpoint directly to the internet - place it behind a TLS-terminating reverse proxy or VPN and restrict inbound connections to known charge-point source networks via firewall allow-listing (trade-off: requires inventory of legitimate station egress IPs and may complicate onboarding new chargers). Enforce mutual TLS (mTLS) client certificates per charge point so identity no longer relies on a guessable station ID (trade-off: certificate provisioning/rotation overhead). Add rate-limiting and connection caps on the WebSocket/OCPP listener to blunt the DoS flooding path (trade-off: aggressive limits may drop legitimate reconnect storms after outages), and monitor for duplicate concurrent sessions using the same station identifier as an indicator of impersonation.

Affected VersionsENISA

EVoke CSMS All versions

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Evoke CSMS is a Charging Station Management System (CSMS) - the cloud/server backend that EV charge points connect to, typically over the OCPP protocol carried on WebSocket (ws/wss) connections. In OCPP, each charge point authenticates/associates itself using a ChargePoint/station identity string. Here the backend keys WebSocket sessions on that charging-station identifier and additionally permits multiple endpoints to bind the same session identifier concurrently. The root cause maps to CWE-613 (Insufficient Session Expiration / weak session management): because the identifier space is predictable (station IDs are guessable, not random secrets) and sessions are neither uniquely bound nor properly invalidated on reuse, session identity becomes forgeable. The single affected product is identified by CPE cpe:2.3:a:evoke:evoke_csms:*:*:*:*:*:*:*:* (all versions per available data).

Know when Evoke Csms gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (icscert) PRIMARY 6.9 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 7.3 HIGH

Network-reachable WebSocket, no auth (PR:N) due to predictable guessable session IDs, low complexity; impersonation gives limited C/I and the flooding path gives limited A.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (icscert).

CVSS VectorVendor: icscert

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Severity Changed
Jun 25, 2026 - 22:22 NVD
HIGH MEDIUM
CVSS changed
Jun 25, 2026 - 22:22 NVD
7.3 (HIGH) 6.9 (MEDIUM)

DescriptionCVE.org

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. 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.

Executive ViewAI

Why It Matters

Evoke CSMS, a critical electric-vehicle charging management system, contains an unauthenticated authentication bypass vulnerability allowing attackers to impersonate legitimate charging stations and users, or launch denial-of-service attacks against the backend infrastructure. This exposes your charging network to operational disruption and unauthorized access with no vendor patch currently available, creating immediate risk to fleet operations and customer access.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Network segmentation-restrict WebSocket endpoint access via firewall rules to authorized admin networks only; (2) Rate limiting-enforce strict connection throttles on session creation endpoints to prevent enumeration and resource exhaustion; (3) Monitoring-deploy anomaly detection on session reuse patterns and failed authentication attempts; (4) Access controls-require VPN or IP allowlisting for CSMS administrative access; (5) If operations-critical, temporarily restrict CSMS to read-only mode or offline procedures pending patch availability.

Threat Intelligence Overview

EPSS Score
0.2%
Top 84% exploitable
Prevalence
Low
niche EV charging station management backend, industry-specific deployment
Threat Intel
1
1 sources
Social Media
2
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat Yes
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: +10
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Threat IntelligenceMISP

CISA Advisories
Sources: CISA (public domain), CISA Vulnrichment

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy