What is the CVSS score of CVE-2026-24912?

CVE-2026-24912 has a CVSS 4.0 base score of 6.9 (Medium). CVSS vector: 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. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-24912?

Within 24 hours: Identify and inventory all systems using the affected WebSocket backend and assess which charging stations are exposed; notify relevant operations teams of the risk. Within 7 days: Implement network segmentation to restrict WebSocket endpoint access and deploy WAF rules to detect anomalous multi-endpoint connections using duplicate session IDs. Within 30 days: Develop and test session validation logic that enforces one-to-one session-to-endpoint binding; monitor vendor communications for patch availability and prepare deployment procedures.

Epower Ie CVE-2026-24912

MEDIUM

Insufficient Session Expiration (CWE-613)

2026-03-06 ics-cert@hq.dhs.gov

Authentication Bypass Epower Ie Epower

6.9

CVSS 4.0 · NVD

View

Attack ChainAIDerived

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

Access

Connect to WebSocket backend with known charging station identifier
Exploit

Reuse predictable session identifier from legitimate station
Execution

Displace active session through most recent connection
Impact

Receive backend commands intended for legitimate station

Vulnerability Assessment

Weakness	CWE CWE-613 OWASP Top 10:2025 A07:2025 - Authentication Failures ASVS 5.0 V7 - Session Management Session expiration enforcement
Exploitation Conditions	WebSocket backend accepting multiple concurrent connections with identical charging station identifiers; predictable session identifier generation without per-connection validation or conflict detection mechanisms.
Impact	CVSS 7.3 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: None. User interaction: None. Exploitation no authentication required.
Exploit ScenarioDerived	An attacker without authentication could exploit this vulnerability to authenticate as other users or enable a malicious actor to cause a denial-of-ser.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).

No patch listed yet 0.0% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Mar 12, 2026

WebSocket session handling in charging station backends accepts duplicate session identifiers, allowing attackers to hijack active sessions and intercept commands intended for legitimate stations or impersonate authenticated users. An unauthenticated remote attacker can exploit this predictable session management to displace legitimate connections, redirect backend communications, or launch denial-of-service attacks by flooding the system with valid session requests. No patch is currently available.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:06 CVSS 7.3

The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. [CVSS 7.3 HIGH]

RemediationAI

Monitor vendor advisories for a patch. Restrict network access to the affected service where possible.

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

Classified as CWE-613 (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 malicio

Know when Epower Ie 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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 6.9 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Severity Changed

May 06, 2026 - 14:52 NVD

HIGH MEDIUM

CVSS changed

May 06, 2026 - 14:52 NVD

7.3 (HIGH) 6.9 (MEDIUM)

CVE Published

Mar 06, 2026 - 00:16 nvd

HIGH 7.3

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

Executive ViewAI

Why It Matters

CVE-2026-24912 allows attackers to hijack WebSocket sessions in charging station management systems by connecting multiple endpoints with identical session identifiers, potentially enabling unauthorized control or monitoring of critical infrastructure. This vulnerability directly impacts the integrity and availability of EV charging networks and could expose operational systems to malicious interference without immediate patching options.

Business Impact: High

Compensating Controls

Implement Web Application Firewall (WAF) rules to detect and block multiple simultaneous connections from different source IPs using identical session identifiers; enforce network segmentation restricting WebSocket traffic to authorized subnets only; deploy enhanced session logging and monitoring to detect anomalous connection patterns; consider temporarily restricting remote WebSocket access to essential administrative functions only until patch availability; implement rate limiting on session creation and IP-based connection throttling.

Threat Intelligence Overview

EPSS Score

0.0%

Top 86% exploitable

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

VulDB

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

Patch available No

Active threat No

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.