LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22890: EV2GO ev2go.io Insufficiently Protected Credentials

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

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22890 concerns EV2GO ev2go.io charging stations where authentication identifiers are publicly accessible through web-based mapping platforms. In business terms, information that should help prove charging-station identity or access may be exposed publicly, creating risk of unauthorized activity or trust failure around charging infrastructure.

Executive priority

Treat this as a medium-priority operational technology exposure. Prioritize organizations with public EV charging assets or financial exposure from unauthorized charging. The immediate goal is reducing public credential exposure and confirming vendor guidance.

Technical view

The issue is classified as CWE-522: insufficiently protected credentials. The CVSS 4.0 score is 6.9, medium severity, with network exposure, low attack complexity, no privileges, and no user interaction required. Reported impacts are low confidentiality and integrity impact, with no availability impact listed.

Likely exposure

Organizations using EV2GO ev2go.io charging infrastructure may be exposed if station authentication identifiers appear in public web mapping platforms. The source bundle lists EV2GO ev2go.io as affected across all versions, but also includes limited product detail.

Exploitation context

CISA KEV is false, and the provided sources do not state active exploitation. The risk is practical exposure of authentication identifiers, not a confirmed exploit campaign. Public availability lowers discovery effort for anyone reviewing mapping data.

Researcher notes

Evidence is limited to the CVE record, CISA advisory reference, and CSAF link in the source bundle. Do not assume a patch exists unless confirmed by EV2GO or CISA. The contradiction between affected all versions and defaultStatus should be verified against the advisory.

Mitigation direction

  • Check EV2GO and CISA guidance for official remediation or configuration changes.
  • Remove authentication identifiers from public mapping platforms where possible.
  • Rotate exposed identifiers or credentials if EV2GO supports rotation.
  • Review charging-station access controls and restrict unnecessary public data exposure.
  • Monitor charging activity, billing, and administrative events for anomalies.

Validation and detection

  • Inventory EV2GO ev2go.io charging stations and related accounts.
  • Review public mapping entries for exposed authentication identifiers.
  • Confirm identifiers are not present in public descriptions, metadata, or station profiles.
  • Check logs for unusual charging sessions or administrative changes.
  • Document whether vendor remediation guidance has been applied.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-522: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22890 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-22890Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EV2GOev2go.ioAll versionsunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-522 · source CWE mapping

Insufficiently Protected Credentials

Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.