Authenticated client disconnection via Client ID reuse
Published Apr 19, 2026 · Updated Apr 19, 2026
Session handling in EMQ EMQX Enterprise 6.0 and 6.1.0 allows remote authenticated users to disconnect another MQTT client. A second connection using the target's Client ID replaces the existing broker session because the identifier is not bound to the authenticated username. The report requires valid MQTT credentials and knowledge or guessing of the target ID; EMQ disputes the CVE and calls the result required MQTT takeover behavior.
Summary
What happened
Session handling in EMQ EMQX Enterprise 6.0 and 6.1.0 allows remote authenticated users to disconnect another MQTT client. A second connection using the target's Client ID replaces the existing broker session because the identifier is not bound to the authenticated username. The report requires valid MQTT credentials and knowledge or guessing of the target ID; EMQ disputes the CVE and calls the result required MQTT takeover behavior.
The record
- CVE
- CVE-2026-6564
- Published
- Apr 19, 2026
- Updated
- Apr 19, 2026
- Vendor
- EMQ
- Product
- EMQX Enterprise
- Classifications
- CWE-285, CWE-266, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2026CVE publishedPublication date reported by the CVE source.
- Apr 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0
- Affected versionversion=6.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- mqtt_user_vs_clientid.pyproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo