CVE-2026-67418

published 14 Oct 2026 · updated 25 Oct 2026

RabbitMQ MQTT 5: inapplicable PUBLISH property disconnects matching subscribers

5.3MediumCVSS 5.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, the MQTT 5 parser in deps/rabbitmq_mqtt/src/rabbit_mqtt_packet.erl accepts Request-Problem-Information on PUBLISH packets even though the property is valid only for CONNECT. An authenticated publisher with topic write permission can cause the broker to store and route that inapplicable property to a separately authenticated matching subscriber. When the subscriber path serializes the outbound PUBLISH, serialise_prop/2 has no matching clause, and the uncontained function_clause exception closes the victim MQTT or Web MQTT connection. The publisher connection and broker remain available, and queued replay, retained-message persistence, and broker-wide denial of service were not established. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=3.13.0 <3.13.19, >=4.0.0 <4.0.24, >=4.1.0 <4.1.15, >=4.2.0 <4.2.10, >=4.3.0 <4.3.5

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67418 severity on Zeptric[![CVE-2026-67418](https://zeptric.io/badge/cve/CVE-2026-67418.svg)](https://zeptric.io/cve/CVE-2026-67418)