CVE-2026-20748: api.everon.io · CWE-613
Affects api.everon.ioSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% 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 |
|---|---|---|
| Everonapi.everon.io | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-20748, organizations should implement the following specific measures: 1) Enforce unique, unpredictable session identifiers that cannot be reused or guessed, ensuring that only one active session per charging station identifier is allowed at any time. 2) Implement strict session expiration and invalidation policies to prevent stale or duplicated sessions. 3) Introduce mutual authentication mechanisms between charging stations and the backend to verify the legitimacy of connections before accepting commands. 4) Monitor WebSocket connections for abnormal patterns such as multiple simultaneous connections using the same identifier or excessive session requests indicative of DoS attempts. 5) Employ rate limiting and connection throttling on the backend to mitigate flooding attacks. 6) If possible, isolate critical backend components behind additional authentication layers or network segmentation to reduce exposure. 7) Engage with Everon for updates or patches addressing this vulnerability and apply them promptly once available. 8) Conduct regular security assessments and penetration testing focused on session management and WebSocket communication security. These targeted actions go beyond generic advice and address the root causes of the vulnerability.
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.