LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25711: Chargemap chargemap.com 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-25711 affects Chargemap’s chargemap.com WebSocket backend. Sessions are tied to charging station identifiers in a way that may let another endpoint connect with the same identifier and displace the legitimate station. Business impact could include disrupted charging operations and unauthorized receipt of backend commands. Public sources do not indicate active exploitation.

Executive priority

Treat this as a high-priority operational technology exposure if your business depends on Chargemap-connected charging services. The main concern is disruption or misdirected backend commands, not confirmed widespread exploitation. Assign ownership to validate exposure with Chargemap and monitor for vendor remediation.

Technical view

The issue is classified as CWE-613, insufficient session expiration. CISA describes predictable or reusable station-session identifiers that allow multiple endpoints to use the same session identifier. The newest connection can shadow or replace the legitimate station connection. CVSS 3.1 is 7.3, network exploitable, low complexity, no privileges, no user interaction.

Likely exposure

Exposure is most relevant to organizations using Chargemap-connected charging stations or relying on Chargemap’s backend services. The source bundle lists Chargemap chargemap.com as affected across all versions, but also includes an inconsistent default status. Validate directly with Chargemap and CISA’s advisory before making scope decisions.

Exploitation context

The vulnerability is remotely reachable over the network and does not require credentials or user interaction according to the CVSS vector. CISA and the CVE description describe session hijacking, session shadowing, command interception, and denial-of-service potential. The source bundle marks KEV as false, and no cited source states active exploitation.

Researcher notes

Evidence is limited to the CVE, CISA advisory references, and CSAF link in the bundle. No public exploit status, patch version, or detailed vendor mitigation is provided here. Avoid assuming all deployments are affected until Chargemap or CISA clarifies scope and fixed status.

Mitigation direction

  • Review CISA advisory ICSA-26-057-05 for vendor-specific updates.
  • Contact Chargemap support for confirmed remediation or configuration guidance.
  • Do not assume a patch exists unless Chargemap or CISA confirms one.
  • Monitor for duplicate connections using the same charging station identifier.
  • Prioritize compensating monitoring for operationally critical charging sites.

Validation and detection

  • Inventory charging stations and services integrated with Chargemap.
  • Confirm whether your environment uses the affected WebSocket backend.
  • Review backend logs for repeated station identifier reuse.
  • Look for legitimate station connections being displaced unexpectedly.
  • Track CISA CSAF and Chargemap support pages for status changes.
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-25711 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-25711Attack 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
Chargemapchargemap.comAll 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.