LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27652: CloudCharge cloudcharge.se 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

CloudCharge cloudcharge.se has a session handling flaw in its WebSocket backend. A connecting endpoint can reuse another charging station’s identifier, potentially taking over or shadowing that station’s backend session. Business impact includes disrupted EV charging operations, misdirected backend commands, limited data exposure, and service denial risk.

Executive priority

Prioritize within normal emergency patch governance for EV charging environments. The issue can disrupt service and misdirect operational commands, but public sources provided do not confirm exploitation or a named patch. Focus first on exposed production systems and vendor confirmation.

Technical view

CVE-2026-27652 is CWE-613, insufficient session expiration. The backend associates WebSocket sessions with charging station identifiers and permits multiple endpoints using the same session identifier. The newest connection can displace the legitimate station and receive commands intended for it. CVSS 3.1 is 7.3: network exploitable, low complexity, no privileges, no user interaction.

Likely exposure

Organizations using CloudCharge cloudcharge.se should treat deployments as potentially exposed, with the CVE record listing all versions affected. Exposure is most relevant where charging station WebSocket connectivity is reachable by untrusted networks or identifiers can be observed, guessed, or reused.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not listed as KEV in the bundle. The vulnerability is remotely reachable and requires no privileges or user interaction according to CVSS, making it operationally important even without confirmed exploitation.

Researcher notes

Avoid assumptions beyond the advisory record. Key validation areas are session identifier predictability, duplicate identifier handling, and whether a later WebSocket connection supersedes an existing station session. Do not test against production charging infrastructure without authorization and safety controls.

Mitigation direction

  • Review CISA advisory ICSA-26-057-03 and CloudCharge support guidance for vendor-approved remediation.
  • Limit charging station backend connectivity to trusted networks where operationally feasible.
  • Monitor for duplicate or unexpected station session identifiers and connection displacement events.
  • Coordinate with CloudCharge on patched versions, configuration changes, or compensating controls.

Validation and detection

  • Inventory CloudCharge cloudcharge.se deployments and confirm affected version status with vendor guidance.
  • Check logs for simultaneous connections using the same charging station identifier.
  • Review WebSocket session lifecycle controls for uniqueness, expiration, and replacement behavior.
  • Verify monitoring alerts for station disconnects, unexpected reconnects, or backend command misrouting.
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-27652 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-27652Attack 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
CloudChargecloudcharge.seAll 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.