Read the docs
TI-2026-74321 Aliases CVE-2026-67418

RabbitMQ MQTT 5 PUBLISH property disconnects matching subscribers

Priority LOW 24CWE-1286Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · Low
Fix status
Partial Red Hat: 1 fixed, 5 without a fix

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-248.

Summary

RabbitMQ server versions from 3.13.0 before 3.13.19, from 4.0.0 before 4.0.24, from 4.1.0 before 4.1.15, from 4.2.0 before 4.2.10, and from 4.3.0 before 4.3.5 accept the Request-Problem-Information property on MQTT 5 PUBLISH packets, although the property is valid only for CONNECT. The subscriber path has no handler for this property, so an uncaught exception (CWE-248) closes the subscriber's MQTT or Web MQTT connection. An authenticated publisher with topic write permission can trigger this for a separately authenticated matching subscriber, while the publisher connection and broker remain available.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.004 34th percentileScored 2026-11-08
Fix Partial rabbitmq-server (rabbitmq): 3.13.19, 4.0.24, 4.1.15 +2Red Hat: 1 advisoryRed Hat: 1 fixed, 5 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
rabbitmqrabbitmq-server3.13.0 to before 3.13.19; 4.0.0 to before 4.0.24; 4.1.0 to before 4.1.15; 4.2.0 to before 4.2.10; 4.3.0 to before 4.3.53.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5Patch availableCNA
  • rabbitmq-server Vendorrabbitmq Affected 3.13.0 to before 3.13.19; 4.0.0 to before 4.0.24; 4.1.0 to before 4.1.15; 4.2.0 to before 4.2.10; 4.3.0 to before 4.3.5 Fixed in 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*——Broadcom
  • cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* Versions — — ·Broadcom

Remediation

Upgrade RabbitMQ server to 3.13.19, 4.0.24, 4.1.15, 4.2.10, or 4.3.5, depending on the release line in use. Red Hat advisory RHSA-2026:82703 fixes Red Hat Hardened Images, while Red Hat OpenStack Platform 13 (Queens), 16.2, and 17.1 have no fix planned and Red Hat OpenStack Platform 18.0 has none available.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA rabbitmq-server (rabbitmq) Fixed in 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5

Red Hat 1 advisory

  • RHSA-2026:82703 Released 2026-10-14 · Red Hat rating Moderate
    Red Hat Hardened Images RPMs bug fix and enhancement update
    • Red Hat Hardened Images rabbitmq-server4.3-4.3.6-1.1.hum1@aarch64, rabbitmq-server4.3-4.3.6-1.1.hum1@s390x, rabbitmq-server4.3-4.3.6-1.1.hum1@src +1

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Hardened ImagesAffectedNo fix planned: Will not fix
Red Hat OpenStack Platform 13 (Queens)AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 16.2AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 17.1AffectedNo fix planned: Out of support scope
Red Hat OpenStack Platform 18.0AffectedNo fix yet: Fix deferred
Red Hat Hardened ImagesFixed RHSA-2026:82703

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-67418
  2. 2026-10-18 Fix available: RHSA-2026:82703 · Red Hat
  3. 2026-10-18 Fix available: Red Hat Hardened Images · Red Hat
  4. 2026-10-18 CVSS score added · Red Hat

References

Other 6

  • TI-2026-41154 Improper authentication in rabbitmq-server CVSS 3.1CRITICAL 10.0
  • TI-2026-41149 RabbitMQ: UNC SSRF affecting the management UI on Windows CVSS 3.1CRITICAL 10.0
  • TI-2026-41158 Resource allocation without limits in rabbitmq-server CVSS 3.1HIGH 7.5
  • TI-2026-47695 RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint CVSS 4.0HIGH 8.2
  • TI-2026-47694 RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS CVSS 4.0HIGH 8.2
  • TI-2026-45167 RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading CVSS 4.0HIGH 7.5
See all 100 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences