Broker crash via unbounded persistent sessions
Published Dec 3, 2024 · Updated Apr 3, 2026
Denial of service in Mochi MQTT Server 2.6.3 allows remote attackers to exhaust memory and crash the broker through persistent MQTT sessions. The broker retains publish/subscribe session state without an effective aggregate resource bound as malicious long-lived sessions accumulate. Reachability requires an MQTT listener that accepts attacker-controlled sessions; successful abuse exhausts process memory and interrupts all broker service.
Summary
What happened
Denial of service in Mochi MQTT Server 2.6.3 allows remote attackers to exhaust memory and crash the broker through persistent MQTT sessions. The broker retains publish/subscribe session state without an effective aggregate resource bound as malicious long-lived sessions accumulate. Reachability requires an MQTT listener that accepts attacker-controlled sessions; successful abuse exhausts process memory and interrupts all broker service.
The record
- CVE
- CVE-2024-50948
- Published
- Dec 3, 2024
- Updated
- Apr 3, 2026
- Vendor
- Mochi MQTT
- Product
- Mochi MQTT Server
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 3, 2024CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=2.6.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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