CVE-2026-27649: CTEK Chargeportal · CWE-613
Affects CTEK ChargeportalSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 1 Nov 2026, 11:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CTEKChargeportal | Affected
| Fixed in– |
GitHubctek/Chargeportalpkg:github/ctek/ChargeportalOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-27649, organizations should implement the following specific measures: 1) Enforce unique session identifiers per endpoint and disallow multiple simultaneous connections using the same session ID to prevent session shadowing. 2) Implement strong, unpredictable session ID generation mechanisms to eliminate predictability and reduce hijacking risk. 3) Introduce authentication and authorization controls on WebSocket connections to verify endpoint legitimacy before establishing sessions. 4) Monitor and rate-limit session connection attempts to detect and block flooding or denial-of-service attempts. 5) Employ network segmentation and firewall rules to restrict access to the Chargeportal backend only to trusted sources. 6) Work with CTEK to obtain patches or updates addressing this vulnerability once available. 7) Conduct regular security assessments and penetration testing focused on session management and WebSocket security. 8) Maintain detailed logging and alerting on session anomalies to enable rapid incident response.
Description
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.