Microsoft security update for CVE-2025-10543
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-10543. This page also shows what EchelonGraph holds for CVE-2025-10543, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products9
- azl3 influxdb 2.7.5-10 on Azure Linux 3.0
- azl3 influxdb 2.7.5-8 on Azure Linux 3.0
- azl3 telegraf 1.31.0-10 on Azure Linux 3.0
- azl3 telegraf 1.31.0-11 on Azure Linux 3.0
- azl3 telegraf 1.31.0-12 on Azure Linux 3.0
- cbl2 influxdb 2.6.1-24 on CBL Mariner 2.0
- cbl2 influxdb 2.6.1-27 on CBL Mariner 2.0
- cbl2 telegraf 1.29.4-17 on CBL Mariner 2.0
- cbl2 telegraf 1.29.4-18 on CBL Mariner 2.0
✅ Updates Microsoft lists: 5 updates
5 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 2.6.1-26 |
| — | Security Update | 1.31.0-12 |
| — | Security Update | 2.6.1-27 |
| — | Security Update | 1.29.4-18 |
| — | Security Update | 2.7.5-10 |
🧭 EchelonGraph on CVE-2025-10543
- EchelonGraph score
- 5.3 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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).
Published by Eclipse Foundation, the CVE Numbering Authority that assigned CVE-2025-10543, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).