CVE-2026-67418
Description
RabbitMQ's MQTT 5 property parser accepts properties without checking whether they are valid for the enclosing packet type. An authenticated publisher can include `Request-Problem-Information` (MQTT property 0x17) in a `PUBLISH` — a property that the MQTT 5 specification restricts to `CONNECT` — and the broker will store and route it. When a matching subscriber's reader later serializes the outbound `PUBLISH`, `serialise_prop/2` has **no clause** for `Request-Problem-Information`, raising `error:function_clause`. That exception is not contained at the victim queue-event boundary, so the **victim's entire MQTT connection** is closed. The publisher's connection and the broker remain healthy.
CVSS Base Scores
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Affected Products
| Vendor | Product | Version | Status |
|---|---|---|---|
| rabbitmq | RabbitMQ | >= 3.13.0, < 3.13.19 | affected |
| rabbitmq | RabbitMQ | >= 4.0.0, < 4.0.24 | affected |
| rabbitmq | RabbitMQ | >= 4.1.0, < 4.1.15 | affected |
| rabbitmq | RabbitMQ | >= 4.2.0, < 4.2.10 | affected |
| rabbitmq | RabbitMQ | >= 4.3.0, < 4.3.5 | affected |
References
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-jv99-v328-mvmm
- https://github.com/rabbitmq/rabbitmq-server/pull/17035
- https://github.com/rabbitmq/rabbitmq-server/pull/17287
- https://github.com/rabbitmq/rabbitmq-server/commit/4639a4318c72a0660e4bc014767fad70ce288fbc
- https://github.com/rabbitmq/rabbitmq-server/commit/908f944a1d581d10774f8d6d0dcf2a1a713779fb
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5


