This Eclipse Foundation Project adheres to the Eclipse Foundation Vulnerability Reporting Policy.

If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure.

Please do not report security vulnerabilities through public issues, discussions, or change requests.

Instead, report it using one of the following ways:

• Create a confidential issue in the Eclipse Foundation Vulnerability Reporting Tracker

You can find more information about reporting and disclosure at the Eclipse Foundation Security page.

Please include as much of the information listed below as you can to help us better understand and resolve the issue:

• The type of issue (e.g., buffer overflow, protocol violation, denial of service)
• Affected version(s)
• Impact of the issue, including how an attacker might exploit the issue
• Step-by-step instructions to reproduce the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Full paths of source file(s) related to the manifestation of the issue
• Configuration required to reproduce the issue
• Log files that are related to this issue (if possible)
• Proof-of-concept or exploit code (if possible)

This information will help us triage your report more quickly.

If exploitation requires a malicious or compromised broker, explain the additional impact beyond what that broker can already cause through normal MQTT traffic. For example, memory use from a large CONNACK may not represent an additional risk if a large PUBLISH can cause the same effect under equivalent conditions and configured limits.

Bypassing intended limits, disproportionate resource use, or crossing other trust boundaries may still be security relevant. If in doubt, use the confidential reporting process above.

Only the most recent release of the client will be supported with security updates.