Medium · CVSS 6.9CVE-2026-44622

EVoke Systems EVoke CSMS Insufficiently Protected CredentialsCVE-2026-44622

Answer in brief

CVE-2026-44622 records a Medium severity (CVSS 6.9) vulnerability in EVoke Systems EVoke CSMS Insufficiently Protected Credentials. The current sources do not mark it as known exploited. The current feed maps EVoke/EVoke CSMS (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jun 25, 2026Updated Oct 25, 2026Source checked Nov 3, 2026First seen by HOL Jun 25, 2026Material review Oct 25, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps EVoke/EVoke CSMS (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
EVoke/EVoke CSMSgeneric	All versions	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for EVoke/EVoke CSMS.
Review the reported fix. Source-reported solutions: EVoke states that as a hardware-agnostic platform supporting multiple charger Original Equipment Manufacturers OEMs, EVoke must interoperate with EVSE devices that support different OCPP security profiles depending on the firmware capabilities of the charger. EVoke CSMS currently supports all OCPP security profiles (0–3). However, the effective security configuration for a charger connection is determined by the security profile implemented in the EVSE firmware. Some legacy chargers deployed in the network support only Security Profile 0 or 1. These chargers were installed prior to the broader industry adoption of stronger authentication mechanisms defined in OCPP Security Profiles 2 and 3. EVoke is actively working with charger OEM partners to migrate supported devices to Security Profile 2 (TLS encryption with basic authentication) or Security Profile 3 (Mutual TLS authentication using client certificates). For OEMs that continue to support firmware updates, EVoke will prioritize upgrades to enable Security Profiles 2 or 3. EVoke states that certain legacy charger models deployed on the network are no longer supported by the manufacturer (for example, chargers originally produced by EVBox). These devices cannot be upgraded to support stronger security profiles. For chargers limited to Security Profiles 0 or 1, EVoke is implementing additional server-side protections to mitigate spoofing risks. Allow-listed chargers will only be accepted from chargers whose IDs are registered in the EVoke CSMS inventory database. Unknown charger identifiers will be rejected.

Evidence timeline and material changes

Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 25, 2026

Sources and claim methodology

Upstream source description

Charging station authentication identifiers are publicly accessible via web-based mapping platforms.

Quoted source text, attributed separately from HOL analysis.

Package

Affected range

Fixed version

EVoke/EVoke CSMSgeneric

All versions

Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for EVoke/EVoke CSMS.

Review the reported fix. Source-reported solutions: EVoke states that as a hardware-agnostic platform supporting multiple charger Original Equipment Manufacturers OEMs, EVoke must interoperate with EVSE devices that support different OCPP security profiles depending on the firmware capabilities of the charger. EVoke CSMS currently supports all OCPP security profiles (0–3). However, the effective security configuration for a charger connection is determined by the security profile implemented in the EVSE firmware. Some legacy chargers deployed in the network support only Security Profile 0 or 1. These chargers were installed prior to the broader industry adoption of stronger authentication mechanisms defined in OCPP Security Profiles 2 and 3. EVoke is actively working with charger OEM partners to migrate supported devices to Security Profile 2 (TLS encryption with basic authentication) or Security Profile 3 (Mutual TLS authentication using client certificates). For OEMs that continue to support firmware updates, EVoke will prioritize upgrades to enable Security Profiles 2 or 3. EVoke states that certain legacy charger models deployed on the network are no longer supported by the manufacturer (for example, chargers originally produced by EVBox). These devices cannot be upgraded to support stronger security profiles. For chargers limited to Security Profiles 0 or 1, EVoke is implementing additional server-side protections to mitigate spoofing risks. Allow-listed chargers will only be accepted from chargers whose IDs are registered in the EVoke CSMS inventory database. Unknown charger identifiers will be rejected.

Sources and claim methodology

Upstream source description

Charging station authentication identifiers are publicly accessible via web-based mapping platforms.

Quoted source text, attributed separately from HOL analysis.