# CVE-2026-40702: EVoke Systems EVoke CSMS Missing Authentication for Critical Function

> Attackers can impersonate charging stations via unauthenticated WebSocket endpoints to access sensitive data and escalate privileges in EVoke CSMS.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-v97x-26qp-3g45

## What is CVE-2026-40702?

CVE-2026-40702 is a critical missing authorization vulnerability in EVoke CSMS, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WebSocket endpoints lack proper authentication mechanisms, enabling attackers to impersonate charging stations. As a result, attackers can exploit this weakness to gain unauthorized access to sensitive data or perform unauthorized actions. Given that no authentication is required, this can lead to privilege escalation and potentially compromise the security of the entire system.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-40702?


## How do I fix CVE-2026-40702?

No fix has been published for CVE-2026-40702 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40702 being exploited?

There is no known exploitation of CVE-2026-40702 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40702 and fix it if it is affected.

What it is: CVE-2026-40702 is a critical missing authorization vulnerability in EVoke CSMS, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40702 in the wild and no public exploit code.

Affected product: EVoke CSMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40702/ (Markdown: https://insights.sbomify.com/CVE-2026-40702/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40702
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40702
- OSV: https://osv.dev/vulnerability/CVE-2026-40702

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40702/
Summaries are generated and may contain mistakes; the official description above is the record.