VulnerabilityPublished 26 Feb 2026Updated 5 Mar 2026

CVE-2026-22890: ev2go.io · CWE-522

Affects ev2go.ioSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
EV2GOev2go.io	Affected =All versions	Fixed in–

AI-suggested

To mitigate CVE-2026-22890, organizations should immediately audit and restrict access to authentication identifiers on all web-based mapping platforms and APIs associated with EV2GO services. EV2GO should implement strict access controls, ensuring that sensitive identifiers are never publicly exposed or embedded in publicly accessible resources. Employing tokenization or encryption for authentication data in transit and at rest is critical. Organizations should monitor network traffic and logs for unusual access patterns to charging station credentials. Implementing multi-factor authentication and anomaly detection on charging station management systems can reduce the risk of unauthorized access. EV2GO should prioritize releasing patches or updates that remove or obfuscate authentication identifiers from public interfaces. Additionally, organizations should engage in threat hunting and incident response preparedness specific to EV infrastructure. Collaboration with EV2GO and relevant cybersecurity authorities to share intelligence and coordinate response efforts is recommended. Finally, educating staff and users about the risks associated with exposed credentials can help reduce social engineering or related attack vectors.

Description

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

Impact

The primary impact of CVE-2026-22890 is the exposure of authentication identifiers for EV charging stations, which can lead to unauthorized access or manipulation of these stations. This compromises confidentiality by revealing sensitive credentials and integrity by enabling potential unauthorized commands or configurations. While availability is not directly affected, unauthorized control could indirectly disrupt charging services. For organizations operating EV2GO charging infrastructure, this vulnerability could result in operational disruptions, financial losses, reputational damage, and potential safety risks if charging stations are manipulated maliciously. The exposure also raises privacy concerns for users relying on these stations. Given the increasing adoption of electric vehicles globally, the vulnerability poses a significant risk to critical EV infrastructure, especially in regions with high EV penetration and reliance on EV2GO services. Attackers could leverage this information for targeted attacks, including fraudulent charging sessions or denial of service through indirect means. The lack of authentication or user interaction requirements lowers the barrier for exploitation, increasing the threat landscape.

CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Mar 2026, 20:57 UTC

WeaknessesCWE-522

Technical details

References

Community reviews

Related threats