Security readout for executives and security teams
Plain-English summary
CVE-2026-25945 affects EV2GO ev2go.io. Its WebSocket API reportedly does not limit repeated authentication attempts. That can let an unauthenticated remote attacker overload authentication handling, disrupt charger telemetry, or try repeated guesses for unauthorized access. Public sources rate it high severity; no CISA KEV listing is provided.
Executive priority
Prioritize review for environments where EV charging operations depend on ev2go.io telemetry. The main concern is service disruption and possible unauthorized access pressure, not confirmed compromise. Treat as high priority for exposure confirmation and compensating controls while awaiting or applying official vendor guidance.
Technical view
The issue is CWE-307: improper restriction of excessive authentication attempts in the ev2go.io WebSocket API. The CVSS 4.0 score is 8.7, with network attack vector, low complexity, no privileges, and no user interaction. Reported impact is high availability loss, specifically telemetry suppression or misrouting, plus brute-force risk.
Likely exposure
Organizations using EV2GO ev2go.io, especially for EV charger telemetry or remote charging operations, should assume exposure until vendor guidance says otherwise. The supplied CVE data lists EV2GO ev2go.io “All versions,” but also includes an “unaffected” default status, so asset-specific confirmation is important.
Exploitation context
The sources describe a remotely reachable authentication-rate-limiting weakness. They do not provide evidence of active exploitation, and the CVE is not listed as CISA KEV in the provided data. Business risk is operational disruption to charger telemetry and possible unauthorized access attempts.
Researcher notes
Evidence is limited to the CVE record and CISA advisory references. Do not assume a patch, exploit, or affected deployment details beyond EV2GO ev2go.io. The CVSS vector indicates unauthenticated network reachability and availability impact. Validate real exposure through asset inventory, configuration review, and logs, not active brute-force testing.
Mitigation direction
- Check EV2GO and CISA advisory guidance for official fixes or compensating controls.
- Restrict network access to ev2go.io WebSocket authentication interfaces where operationally possible.
- Monitor authentication volume, failures, and unusual WebSocket session patterns.
- Apply rate limiting or upstream traffic controls if supported by your architecture.
- Prepare operational fallback procedures for charger telemetry disruption.
Validation and detection
- Inventory EV2GO ev2go.io deployments and integrations.
- Confirm whether WebSocket authentication endpoints are internet-reachable.
- Review logs for repeated authentication attempts and telemetry anomalies.
- Verify whether rate limiting exists at application, gateway, or WAF layers.
- Track CISA advisory ICSA-26-057-04 and vendor updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-307: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-25945 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://ev2go.io/CVE reference
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-057-04CVE reference
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-057-04.jsonCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Excessive Authentication Attempts
Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.