dbcve.org
Chargemap.comApplication · Chargemap

CVE-2026-20792

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The WebSocket Application Programming Interface lacks restrictions on the number of authentication requests. This absence of rate limiting may allow an attacker to conduct denial-of-service attacks by suppressing or misrouting legitimate charger telemetry, or conduct brute-force attacks to gain unauthorized access.

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 · high confidence

The WebSocket API lacks rate limiting on authentication requests, allowing unlimited authentication attempts. This enables both brute-force attacks to gain unauthorized access and denial-of-service attacks that can suppress or misroute legitimate charger telemetry.

MitigationImplement rate limiting on WebSocket authentication endpoints with account lockout policies, and deploy monitoring to detect and block brute-force patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Chargemap.comApplication
Affected:all versions

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
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if you run or integrate with Chargemap software
    Check your deployed applications, dependencies, or integrated services for Chargemap Chargemap.com presence. Review any WebSocket client implementations connecting to Chargemap endpoints.
    Affected if You have a deployment or integration using Chargemap Chargemap.com software or API
  2. Locate WebSocket authentication endpoints
    Inspect your WebSocket server configuration or API documentation for authentication-related endpoints (e.g., /ws/auth, /ws/login). Use network inspection tools to capture WebSocket handshake and authentication traffic.
    Affected if WebSocket authentication endpoints exist and accept connection requests
  3. Verify rate limiting is configured on auth endpoints
    Review your WebSocket server configuration files, load balancer settings, or API gateway rules for rate limiting rules on authentication paths. Check for any rate-limit, throttle, or request-limit directives.
    Affected if No rate limiting rules are found on WebSocket authentication endpoints
  4. Review authentication attempt logs for brute-force patterns
    Examine authentication logs, access logs, or security event logs for WebSocket connections. Search for repeated authentication failures from the same source IP or session within short time windows.
    Affected if Logs show many failed authentication attempts without blocking or throttling
  5. Check for account lockout policies
    Inspect your authentication system configuration for account lockout settings after failed attempts. Verify if accounts become temporarily or permanently locked after multiple failures.
    Affected if No account lockout or account temporarily disabled policies are configured for WebSocket authentication
  6. Monitor for abnormal authentication traffic
    Analyze WebSocket connection metrics for sudden spikes in authentication requests, unusual request patterns, or traffic from suspicious sources targeting authentication endpoints.
    Affected if High volumes of authentication requests are observed without protective measures

You are affected if you use Chargemap Chargemap.com and your WebSocket authentication endpoints lack rate limiting, account lockout policies, or brute-force detection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement rate limiting on WebSocket authentication endpoints with account lockout policies, and deploy monitoring to detect and block brute-force patterns.

Fix this in Chargemap.com Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20792 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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