All vulnerabilities
CVE-2026-67418GHSA-jv99-v328-mvmm

rabbitmq-server: RabbitMQ MQTT 5: inapplicable PUBLISH property disconnects matching subscribers

rabbitmq rabbitmq-server
CVSS
5.3Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.40%Chance of exploitation activity in the next 30 days, higher than 33% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
Published14 Oct 2026Updated 14 Oct 2026CVE List

What fixes it

No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.

Description

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.

Text from CVE List

Affected versions 5

  • rabbitmq-serveraffected: >= 3.13.0, < 3.13.19CVE List
  • rabbitmq-serveraffected: >= 4.0.0, < 4.0.24CVE List
  • rabbitmq-serveraffected: >= 4.1.0, < 4.1.15CVE List
  • rabbitmq-serveraffected: >= 4.2.0, < 4.2.10CVE List
  • rabbitmq-serveraffected: >= 4.3.0, < 4.3.5CVE List

References 6