CVE-2026-26288
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 · uneditedWebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend.
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 confidenceWebSocket endpoints for OCPP (Open Charge Point Protocol) lack authentication mechanisms, allowing unauthenticated attackers to connect using a known or discovered charging station identifier and impersonate legitimate chargers. This enables arbitrary command execution and data manipulation within the charging infrastructure.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm use of Everon Api.everon.ioInspect your integration documentation, API configuration, or connection strings to identify if your system connects to Everon's OCPP WebSocket endpoint at api.everon.ioAffected if Your system connects to api.everon.io for OCPP WebSocket communication
-
Test WebSocket connection without credentialsAttempt to establish a WebSocket connection to the Everon OCPP endpoint using a test station identifier without providing any authentication tokens or certificatesAffected if The WebSocket connection is accepted and a session is established without requiring any authentication
-
Verify station identifier acceptance policyConnect to the WebSocket endpoint using a known or fabricated charging station identifier and observe if the system accepts it without validating ownership or authenticationAffected if The system accepts any station identifier without proof of ownership or additional verification
-
Check for authentication enforcement in connection flowReview your integration's connection implementation or the API documentation to determine what authentication mechanism (if any) is required before the WebSocket handshake completesAffected if No mTLS, token-based authentication, or API key validation is required before the WebSocket connection is established
You are affected if your system uses Everon Api.everon.io and accepts WebSocket connections without requiring strong authentication (mTLS, tokens, or API keys) combined with station identifier verification.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strong authentication for WebSocket connections such as mutual TLS (mTLS), token-based authentication, or API key validation, combined with proper station identifier verification to prevent impersonation.
- Consultation8.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26288 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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