dbcve.org
Api.everon.ioApplication · Everon

CVE-2026-20748

HIGH · 8.6 CVSS v3.1 Published 2026-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WebSocket backend for charging stations uses predictable session identifiers tied to station IDs, allowing multiple endpoints to connect with the same session ID. This enables session hijacking where a malicious connection displaces the legitimate station and receives commands intended for it, while also facilitating DoS through repeated valid session requests.

MitigationImplement cryptographically random session identifiers and enforce single-active-session-per-station logic to prevent duplicate connections with the same identifier.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Api.everon.ioApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Everon Api.everon.io usage
    Review your system configuration, integrations, or API endpoint references to determine if your environment connects to or uses Everon Api.everon.io as the backend service for charging station communication.
    Affected if Your system integrates with Everon Api.everon.io for managing charging stations.
  2. Verify WebSocket session handling
    Inspect network traffic or application logs during WebSocket connection establishment with the charging station backend. Capture the session identifier presented during connection handshake.
    Affected if Session identifiers appear sequential, based on station IDs, or otherwise predictable rather than cryptographically random.
  3. Test for duplicate session acceptance
    Attempt to establish multiple WebSocket connections using the same session identifier from different endpoints or client sources. Observe whether the backend accepts both connections or rejects duplicates.
    Affected if The backend permits multiple concurrent connections sharing identical session identifiers tied to the same station.
  4. Check session management configuration
    Review any available configuration settings, API documentation, or backend access controls related to session lifecycle management for charging station connections.
    Affected if No mechanism exists to enforce exactly one active session per station or to invalidate prior sessions upon new connections.

You are affected if your environment uses Everon Api.everon.io and allows multiple WebSocket connections with the same session identifier for a charging station.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement cryptographically random session identifiers and enforce single-active-session-per-station logic to prevent duplicate connections with the same identifier.

Fix this in Api.everon.io Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20748 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data