Update module github.com/eclipse/paho.mqtt.golang to v1.5.1 [SECURITY] - #125
Open
renovate[bot] wants to merge 1 commit into
Open
Update module github.com/eclipse/paho.mqtt.golang to v1.5.1 [SECURITY]#125renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
deleted the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
March 27, 2026 05:36
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
March 30, 2026 17:30
7071ac9 to
03d0002
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
April 26, 2026 14:39
03d0002 to
2e1d387
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
April 27, 2026 22:36
2e1d387 to
da9069d
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
May 20, 2026 15:05
da9069d to
0dce601
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
May 21, 2026 06:00
0dce601 to
682de6a
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
June 23, 2026 21:04
682de6a to
1c20988
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
August 17, 2026 22:43
1c20988 to
389d3c7
Compare
renovate
Bot
force-pushed
the
renovate/go-github.com-eclipse-paho.mqtt.golang-vulnerability
branch
2 times, most recently
from
August 31, 2026 19:05
389d3c7 to
27dbd82
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.0→v1.5.1Eclipse Paho Go MQTT may incorrectly encode strings if length exceeds 65535 bytes
CVE-2025-10543 / GHSA-32fw-gq77-f2f2
More information
Details
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).
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
eclipse/paho.mqtt.golang (github.com/eclipse/paho.mqtt.golang)
v1.5.1Compare Source
This is a minor release incorporating changes made in the 14 months since v1.5.0 (including updating dependencies, and raising the Go version to 1.24). The changes are relatively minor but address a potential security issue (CVE-2025-10543), possible panic, enable users to better monitor the connection status, and incorporate a few optimisations.
Thanks to those who have provided fixes/enhancements included in this release!
Special thanks to Paul Gerste at Sonar for reporting issue #730 via the Eclipse security team (fix was implemented in PR #714 in May, github issue created just prior to this release). This issue arose where a topic > 65535 bytes was passed to the
Publishfunction, due to the way the data was encoded the topic could leak into the message body. Please see issue #730 or CVE-2025-10543 for further details.What's Changed
Full Changelog: eclipse-paho/paho.mqtt.golang@v1.5.0...v1.5.1
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.