Servers and applications
CVE-2026-67418
MQTT 5.0: inapplicable PUBLISH property disconnects matching subscribers
- Severity
- Medium 5.3
- Published
- 18 Aug 2026
- Last changed
- 14 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
- Exploit chance
- 0.4% in the next 30 daysHigher than 35% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Slow it down
- CVSS 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- Also known as
- GHSA-jv99-v328-mvmm
- Sources
- CVE Program, Project advisories (GitHub)
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.
- MQTT (and optionally Web MQTT) is enabled.
- Attacker is an authenticated MQTT 5 client with write permission for a topic.
- Victim is a separately authenticated MQTT 5 (or Web MQTT) client subscribed to that topic (or a matching filter).
There is no packet-type applicability check around parse_prop/2.
Affected software
| Software | Affected versions |
|---|---|
RabbitMQServers and applications · cna:rabbitmq|rabbitmq-server |
|
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server |
|
About RabbitMQ
open source message broker, sometimes referred to as "Rabbit"
- Docker Hub pulls
- 3,918,841,187Docker Hub, 15 Nov 2026
- GitHub stars
- 13,973GitHub, 15 Nov 2026
- Forks
- 4,032GitHub, 15 Nov 2026
- Latest release
- v4.4.0GitHub, 15 Nov 2026
- Released
- 19 Oct 2026GitHub
- Developer
- Jean-Sébastien PédronWikidata
- License
- Mozilla Public License, version 2.0Wikidata
- Written in
- ErlangWikidata
- First published on GitHub
- 20 Sept 2010GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.4 | 4.4.0 | Until 31 Jul 2027 |
| 4.3 | 4.3.7 | Until 31 Jan 2027 |
| 4.2 | 4.2.9 | Ended 31 Jul 2026 |
| 4.1 | 4.1.8 | Ended 30 Jan 2026 |
| 4.0 | 4.0.9 | Ended 30 Apr 2025 |
| 3.13 | 3.13.7 | Ended 30 Sept 2024 |
From endoflife.date.
Vulnerabilities in RabbitMQ
- In our list
- 107
- Published in the last 12 months
- 89
- Critical, last 12 months
- 4
- High, last 12 months
- 22
- Known exploited
- 0
- GHSA-3wxh-g236-vm46LDAP authentication failures allow unauthenticated log amplificationHigh 8.2 25 Oct 2026
- GHSA-g73v-gcjq-2g4hAMQP message conversion can repeatedly disconnect AMQP 0-9-1 consumersMedium 6.3 25 Oct 2026
- GHSA-6wvj-vwrc-wcrmHTML injection in management UI OAuth login warningMedium 5.7 25 Oct 2026
- GHSA-mhh3-4wv2-rrj7SASL credentials are not redacted from `amqp10_client` crash dumps and `sys:get_status` outputMedium 5.7 25 Oct 2026
- GHSA-9h6g-46wc-m2f5Memory DoS via incomplete AMQP 0-9-1 messagesHigh 7.1 25 Oct 2026
- GHSA-j6hc-926v-qwq2RabbitMQ STOMP consumers retain OAuth queue access after JWT expirationMedium 4.9 18 Sept 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67418
- GitHub Advisory Database https://github.com/advisories/GHSA-jv99-v328-mvmm
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-jv99-v328-mvmm