CVE-2025-10543: Medium severity Eclipse Paho Go MQTT vulnerability
In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions <=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet).
The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-10543?
CVE-2025-10543 has been classified as a medium severity vulnerability due to potential data leakage risks.
How do I fix CVE-2025-10543?
To mitigate CVE-2025-10543, upgrade the Eclipse Paho Go MQTT library to versions later than 1.5.0.
What impact does CVE-2025-10543 have on affected systems?
CVE-2025-10543 may lead to unexpected content in MQTT packets, potentially causing data leakage.
Which versions of Eclipse Paho Go MQTT are affected by CVE-2025-10543?
Eclipse Paho Go MQTT versions 1.5.0 and earlier are affected by CVE-2025-10543.
Is there a workaround for CVE-2025-10543?
Currently, the recommended solution for CVE-2025-10543 is to upgrade to a patched version of the library.