Skip to content
Fencer Intel
medium —

CVE-2026-130491 json

Uninitialized heap disclosure in CONNECT through Will payload length truncation

published 18h ago modified 14m ago also EUVD-2026-128507 , GHSA-6hx2-p6j3-qrjg

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository eclipse-mosquitto/mosquitto. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

In Eclipse versions 1.5-1.6.13, 2.0.0-2.0.22 and 2.1.0-2.1.2, the client library libmosquitto does not reject Will messages with payloads greater than 65535 bytes when calling `mosquitto_will_set()` or `mosquitto_will_set_v5()`. This results in up to 65535 bytes of uninitialised heap memory being transmitted as the Will.

This can be mitigated by only passing payloads with a maximum length of 65535 bytes.

Is CVE-2026-130491 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected products

  • Eclipse Foundation Eclipse Mosquitto

Classification

Weakness
  • CWE-908 Use of Uninitialized Resource
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of eclipse-mosquitto/mosquitto published their own advisory on GitHub. Reviewed sources take precedence over it.