CVE-2026-27764: Mobiliti e-mobi.hu · CWE-613
Affects Mobiliti e-mobi.huSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% 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 6 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mobilitie-mobi.hu | Affected
| Fixed in– |
GitHubmobiliti/e-mobi.hupkg:github/mobiliti/e-mobi.huOther 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-27764, organizations should implement the following specific measures: 1) Enforce unique, unpredictable session identifiers that cannot be reused or guessed, ensuring that each session is bound to a single endpoint. 2) Implement strict session management policies that invalidate previous sessions upon new connections using the same identifier to prevent session shadowing. 3) Introduce authentication and authorization mechanisms at the WebSocket connection level to verify the legitimacy of connecting endpoints before allowing session establishment. 4) Monitor and rate-limit connection attempts to the backend to detect and prevent flooding or DoS attacks. 5) Employ network-level protections such as Web Application Firewalls (WAFs) and anomaly detection systems to identify suspicious session behavior. 6) Coordinate with Mobiliti for patches or updates addressing this vulnerability, and apply them promptly once available. 7) Conduct regular security assessments and penetration testing focused on session management and WebSocket communications to identify and remediate similar weaknesses. 8) Educate operational staff about the risks of session hijacking and the importance of monitoring charging station connectivity patterns.
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.