CVE-2026-44622 EVoke Systems EVoke CSMS Insufficiently Protected Credentials
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-44622 and fix it if it is affected.
What it is: CVE-2026-44622 is a medium-severity 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-44622 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-44622/ (Markdown: https://insights.sbomify.com/CVE-2026-44622/index.md)
Charging station authentication identifiers are exposed via public web mapping platforms, allowing attackers to read sensitive credentials.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-44622?
CVE-2026-44622 is a medium-severity 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
Charging station authentication identifiers are publicly accessible via web-based mapping platforms.
Weakness: CWE-522
Which versions are affected by CVE-2026-44622?
How do I fix CVE-2026-44622?
No fix has been published for CVE-2026-44622 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-44622 being exploited?
There is no known exploitation of CVE-2026-44622 in the wild and no public exploit code.
Sources
Also known as GHSA-mr33-r399-w43m.