Skip to content
HiveMQ Release

HiveMQ 4.55.3 Maintenance Release

by HiveMQ TeamNOV 3, 2026

The HiveMQ team is pleased to announce the availability of HiveMQ 4.55.3.

This maintenance release for the 4.55 series includes the following bug fixes and improvements:

HiveMQ Enterprise MQTT Broker

  • Added metrics from nodes that left the cluster to the diagnostic archive, for example, after a node restart or a Kubernetes pod change.
  • Reduced the default metrics interval in the diagnostic archive to 5 seconds for more detailed troubleshooting.
  • Updated the default logback.xml file to write event logs asynchronously to avoid reduced broker performance when many clients connect and disconnect frequently. If you customized your conf/logback.xml file, add the new asynchronous event log configuration manually during the upgrade.
  • Improved HiveMQ broker performance on machines with 8 GB or less of RAM.
  • Fixed an issue where a native memory leak in RocksDB during regular background operations could increase the memory usage of the broker.
  • Fixed an issue where a cluster could stop accepting new or rejoining nodes if a node left the cluster during a join operation or if data replication failed.
  • Fixed an issue where a malformed CONNECT packet could abort active trace recordings.
  • Fixed an issue where consumer spans in distributed tracing were incorrectly marked as failed in some cases.
  • Fixed an issue where, under TCP backpressure, the broker could send MQTT packets such as PINGRESP after it sent a DISCONNECT packet for a keep-alive timeout.
  • Fixed an issue where extension consumers with overlapping topic filters could receive duplicate messages, which affected the Kafka, MongoDB, MySQL, PostgreSQL, Microsoft SQL Server, Data Lake, Snowflake, and Bridge extensions.

HiveMQ Enterprise Security Extension

  • Improved OpenID Connect authentication to accept role claims that contain a single string value, in addition to a list of values.
  • Fixed an issue where a MySQL realm that uses MySQL Connector/J could not connect over TLS when its configuration listed more than one TLS protocol or cipher suite.

HiveMQ Control Center

  • Improved the diagnostic archive creation dialog to provide more options for the information that the archive includes.
  • Improved error handling in the HiveMQ Control Center API to return simpler error responses.
  • Disabled the details views of the Queued Messages and Dropped Messages charts on the Overview dashboard during maintenance mode.
  • Fixed column sorting in the Trace Recordings view so that recordings appear in the selected order.

HiveMQ Enterprise Data Lake Extension

  • Improved the performance of the extension when the log level is set to DEBUG.
  • Fixed an issue where an Azure Blob Storage route repeatedly retried an upload with the same file name if a blob with that name already existed.

HiveMQ Enterprise Extension for Kafka

  • Fixed intermittent load failures of custom transformers with multiple constructors in the Kafka extension by always using the public no-argument constructor.

Have a great day, The HiveMQ Team