Unauthenticated service interrupt via unclosed CONNECT sockets
Published May 18, 2026 · Updated May 18, 2026
Uncontrolled resource consumption in tinyMQTT commit 6226ade allows remote attackers to cause a broker service interrupt via malformed CONNECT packets. The parse_connect_packet function sends Identifier Rejected for a zero-length Client ID with CleanSession set to 0 but returns without ensuring TCP socket closure. Repeated unauthenticated connections retain file descriptors and memory until the broker refuses new clients or becomes unresponsive.
Summary
What happened
Uncontrolled resource consumption in tinyMQTT commit 6226ade allows remote attackers to cause a broker service interrupt via malformed CONNECT packets. The parse_connect_packet function sends Identifier Rejected for a zero-length Client ID with CleanSession set to 0 but returns without ensuring TCP socket closure. Repeated unauthenticated connections retain file descriptors and memory until the broker refuses new clients or becomes unresponsive.
The record
- CVE
- CVE-2025-56352
- Published
- May 18, 2026
- Updated
- May 18, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 2026CVE publishedPublication date reported by the CVE source.
- May 18, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Resource_Exhaustion_Poc.txtproof 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