CVE-2026-27764
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 backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests.
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 confidenceThis is a session management vulnerability in a WebSocket backend for charging station management. The system uses charging station identifiers directly as session identifiers, which are predictable, and permits multiple concurrent connections using the same identifier. This allows an attacker to connect with the same ID as a legitimate station, displacing the real connection and intercepting backend commands intended for that station.
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
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 WebSocket endpoint for charging station managementExamine network traffic or server configuration to locate WebSocket endpoints used by the Mvm Mobiliti E Mobi.hu charging station backend serviceAffected if WebSocket endpoints are exposed and accessible for charging station communication
-
Capture and analyze session identifiersConnect to the WebSocket endpoint and capture the session ID assigned by the server; examine whether the ID follows predictable patterns such as sequential numbers, timestamps, or easily guessable formatsAffected if Session IDs exhibit predictable patterns or lack cryptographic randomness
-
Test for session uniqueness enforcementOpen two concurrent WebSocket connections using the same session identifier obtained from a legitimate station; observe whether the backend accepts both connections or rejects the duplicateAffected if The backend allows multiple simultaneous connections with identical session identifiers
-
Verify session displacement behaviorWith a known session ID active, initiate a new connection from another client using that same ID; check if the original connection is terminated or if commands continue to route to the new connectionAffected if A new connection with a known session ID can displace the legitimate charging station and intercept backend commands
-
Review session management configurationIf access to backend configuration is available, examine session management settings for evidence of single-session-per-identifier enforcement or session invalidation policiesAffected if No session uniqueness policy is configured or enforced in the backend
The environment is affected if the WebSocket backend for Mvm Mobiliti E Mobi.hu accepts predictable session IDs and permits concurrent connections with the same identifier, allowing session displacement.
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 cryptographically random, unique session identifiers with proper session state tracking to prevent concurrent sessions with the same identifier, and add authentication validation before accepting WebSocket connections.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27764 — 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-27764 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