CVE-2025-56352

tinyMQTT Broker Resource Exhaustion via Malformed CONNECT Packet

Published May 18, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
In tinyMQTT commit 6226ade15bd4f97be2d196352e64dd10937c1962 (2024-02-18), the broker mishandles protocol violations during CONNECT packet parsing. When receiving a CONNECT packet with a zero-length Client ID while CleanSession is set to 0, the broker correctly replies with a CONNACK return code 0x02 (Identifier Rejected) but fails to explicitly close the TCP connection. Since the surrounding connection teardown logic is not guaranteed to execute, each such invalid CONNECT attempt leaves the underlying socket open. Repeated attempts cause server-side resource exhaustion due to accumulating file descriptors and memory usage, potentially resulting in denial of service.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title tinyMQTT Broker Resource Exhaustion via Malformed CONNECT Packet
Type Values Removed Values Added
Title Open TCP Connection Leakage Causes Denial of Service in tinyMQTT via Malformed CONNECT
Weaknesses CWE-770
Type Values Removed Values Added
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Justdoit0910
Justdoit0910 tinymqtt
Vendors & Products Justdoit0910
Justdoit0910 tinymqtt
Type Values Removed Values Added
Title Open TCP Connection Leakage Causes Denial of Service in tinyMQTT via Malformed CONNECT
Weaknesses CWE-400
CWE-770
Type Values Removed Values Added
Description In tinyMQTT commit 6226ade15bd4f97be2d196352e64dd10937c1962 (2024-02-18), the broker mishandles protocol violations during CONNECT packet parsing. When receiving a CONNECT packet with a zero-length Client ID while CleanSession is set to 0, the broker correctly replies with a CONNACK return code 0x02 (Identifier Rejected) but fails to explicitly close the TCP connection. Since the surrounding connection teardown logic is not guaranteed to execute, each such invalid CONNECT attempt leaves the underlying socket open. Repeated attempts cause server-side resource exhaustion due to accumulating file descriptors and memory usage, potentially resulting in denial of service.
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
May 18, 2026, 5:27 PM
Reserved
Aug 16, 2025, 12:00 AM
Status
Deferred
Published
May 18, 2026, 4:16 PM
Modified
Nov 4, 2026, 8:10 PM