CVE-2026-20882
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 · uneditedThe 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 mis-routing 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 confidenceThe WebSocket API lacks rate limiting on authentication requests, allowing unlimited authentication attempts from a single client. This vulnerability enables both brute-force attacks to gain unauthorized access and denial-of-service attacks by overwhelming the system, potentially suppressing or mis-routing legitimate charger telemetry.
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 dataall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed productConfirm the system is running Mvm Mobiliti E Mobi.hu by checking application metadata, service name, or startup configuration files that identify the productAffected if The system is confirmed to be Mvm Mobiliti E Mobi.hu and is using WebSocket-based authentication
-
Locate WebSocket endpointsReview API documentation or network traffic to identify WebSocket endpoints, particularly those handling authentication or login requests (often found at paths like /ws/auth, /websocket/login, or similar)Affected if WebSocket endpoints exist that handle authentication without visible rate limiting controls
-
Check rate limiting configurationExamine the server or API gateway configuration files (such as nginx.conf, Apache config, or application-level rate limit settings) for rules that limit authentication attempts on WebSocket upgrade requestsAffected if No rate limiting rules are defined for WebSocket authentication endpoints, or the configuration allows unlimited authentication attempts from a single client IP
-
Test authentication attempt limitsSend multiple sequential WebSocket connection requests with authentication credentials from a single client source and observe if requests are rejected or throttled after a certain number of attemptsAffected if The system accepts unlimited authentication attempts without imposing any throttling, lockout, or request frequency limits
-
Verify account lockout policiesCheck if account lockout policies are configured for failed authentication attempts on the WebSocket authentication endpointAffected if No account lockout or temporary suspension policy exists for repeated failed authentication attempts
The environment is affected if it runs Mvm Mobiliti E Mobi.hu with exposed WebSocket authentication endpoints that do not enforce rate limiting or account lockout controls on authentication requests.
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 dataImplement rate limiting on WebSocket authentication endpoints to restrict the number of authentication attempts per client within a defined time window, combined with account lockout policies.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-20882 — 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-20882 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