dbcve.org
Ev2go.ioApplication · Ev2go

CVE-2026-20895

HIGH · 7.5 CVSS v3.1 Published 2026-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 and permits multiple endpoints to connect with the same session ID. This allows an attacker to establish a newer connection that displaces the legitimate charging station and intercepts backend commands intended for that station, enabling session hijacking or shadowing attacks.

MitigationImplement cryptographically random session identifiers, enforce single active session per charging station, and automatically invalidate prior sessions when a new connection with the same identifier is established.

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
Ev2go.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm Ev2go Ev2go.io deployment
    Identify any Ev2go Ev2go.io charging station management systems or backend services in your environment
    Affected if The product Ev2go Ev2go.io is deployed in any capacity
  2. Verify WebSocket backend is enabled
    Inspect configuration files or running services for WebSocket server functionality serving charging stations (typically ports 8080, 8443, or custom WS endpoints)
    Affected if WebSocket backend for charging stations is actively listening and accepting connections
  3. Analyze session identifier generation
    Review source code or configuration related to session ID creation for WebSocket connections; check if IDs use predictable patterns (sequential, timestamp-based, or low-entropy strings) versus cryptographically random values
    Affected if Session IDs are generated using predictable patterns or non-cryptographic methods
  4. Test for concurrent session reuse
    Establish two separate WebSocket connections using the same session identifier and observe if both are accepted by the backend
    Affected if The backend permits multiple simultaneous connections with identical session IDs
  5. Verify session invalidation behavior
    Connect with a session ID, then open a new connection with the same ID from a different endpoint and check if the original connection remains active or is terminated
    Affected if Prior sessions with the same ID remain active when new connections are established (no automatic invalidation)

Environment is affected if Ev2go Ev2go.io is deployed with WebSocket backend enabled and the session management allows predictable IDs or permits multiple concurrent connections with the same session identifier without invalidating prior sessions.

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, enforce single active session per charging station, and automatically invalidate prior sessions when a new connection with the same identifier is established.

Fix this in Ev2go.io Scoped from the published advisory
  • Consultation2.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,110
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20895 — 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-20895 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