CVE-2026-28204
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCharging station authentication identifiers are publicly accessible via web-based mapping platforms.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceElectric vehicle charging station authentication identifiers (such as API keys, tokens, or credentials) have been inadvertently published and are discoverable through public web-based mapping platforms. This exposure allows unauthorized parties to access the authentication details meant for validating communications between charging stations and backend systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify mapping platform presenceSearch public EV charging mapping platforms (such as PlugShare, ChargeMap, Open Charge Map, or any custom web-based maps) for your organization's charging station locations. Note whether your stations appear on any public platform.Affected if Your charging stations are listed on public web-based mapping platforms
-
Inspect station data for credentialsView the raw data or metadata associated with your charging stations on the mapping platform. Look for fields that may contain API keys, tokens, authentication strings, or credentials. This may be in station details, API endpoints, or embedded URLs.Affected if Authentication identifiers such as API keys, tokens, or credentials are visible in the publicly accessible station data
-
Check for exposed backend URLsExamine the station entries for URLs or endpoints that reference backend communication paths. Look for query parameters, API endpoint URLs, or connection strings that may contain authentication tokens or credentials in plain text.Affected if URLs with embedded authentication parameters or backend endpoints are publicly visible
-
Audit third-party data exportsIf your organization provides charging station data to any third-party platforms or aggregators, review the exported data files for any accidentally included sensitive authentication information before publication.Affected if Sensitive identifiers were included in data exported or provided to third-party mapping platforms
You are affected if your EV charging station authentication identifiers are discoverable by the public on any web-based mapping platform.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataOrganizations should immediately audit and rotate any exposed authentication identifiers, remove sensitive data from publicly accessible mapping platform datasets, and implement proper data sanitization processes before publishing location-based information to third-party platforms.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data