dbcve.org
Ev2go.ioApplication · Ev2go

CVE-2026-25945

CRITICAL · 9.8 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 →
100/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 Application Programming Interface lacks restrictions on the number of authentication requests. This absence of rate limiting may allow an attacker to conduct denial-of-service attacks by suppressing or mis-routing legitimate charger telemetry, or conduct brute-force attacks to gain unauthorized access.

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 · moderate confidence

The WebSocket API in this system lacks rate limiting on authentication requests, enabling attackers to perform unlimited authentication attempts. This vulnerability affects charger telemetry systems and can be exploited to conduct brute-force attacks for unauthorized access or denial-of-service attacks that disrupt legitimate charger communications.

MitigationImplement rate limiting on WebSocket authentication endpoints with exponential backoff and account lockout mechanisms to prevent brute-force attacks, combined with WebSocket-level connection limits and monitoring for anomalous authentication patterns.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 is in use
    Inventory your systems for Ev2go Ev2go.io charger telemetry components. Check software inventory, installed applications, or service documentation for references to Ev2go or Ev2go.io.
    Affected if The product Ev2go Ev2go.io is deployed in your environment.
  2. Identify WebSocket endpoints
    Review your application or API documentation, or perform network traffic analysis to identify WebSocket endpoints used by the Ev2go system. Look for WS:// or WSS:// connections typically used for telemetry communication.
    Affected if WebSocket connections are established to Ev2go Ev2go.io services.
  3. Locate WebSocket authentication endpoint
    Examine the WebSocket handshake or authentication flow in your application code, API specifications, or network captures. Identify the specific path or message used for authenticating to the WebSocket API.
    Affected if A WebSocket authentication endpoint exists that accepts credentials.
  4. Test for rate limiting on authentication
    Send multiple authentication requests via WebSocket in quick succession (e.g., 10-20 attempts in under a minute). Observe whether the system throttles, blocks, or returns rate-limit error responses, or if it accepts all attempts without restriction.
    Affected if The system accepts unlimited authentication attempts without throttling or blocking after multiple rapid requests.
  5. Review authentication logs for anomalies
    Examine application logs, security logs, or WebSocket server logs for the Ev2go system. Look for patterns of repeated failed authentication attempts from a single source that were not blocked or rate-limited.
    Affected if Logs show repeated authentication attempts from a single source that were not mitigated by the system.

Your environment is affected if Ev2go Ev2go.io is deployed and the WebSocket authentication endpoint accepts unlimited rapid requests without imposing rate limits, lockouts, or throttling.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement rate limiting on WebSocket authentication endpoints with exponential backoff and account lockout mechanisms to prevent brute-force attacks, combined with WebSocket-level connection limits and monitoring for anomalous authentication patterns.

Recommended fix Moderate confidence
  1. Implement rate limiting on the WebSocket API to restrict authentication requests (e.g., limit to 5-10 attempts per minute per IP address)
  2. Configure account lockout mechanisms after a defined number of failed authentication attempts (e.g., lock for 15-30 minutes after 5 failed attempts)
  3. Add request throttling at the load balancer or reverse proxy level for WebSocket connections
  4. Implement monitoring and alerting for anomalous authentication patterns on the WebSocket endpoint
  5. Consider implementing progressive delays (exponential backoff) between authentication attempts
  6. Enable detailed logging of authentication failures for security analysis and incident response

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ev2go.io Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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