BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

CVE-2026-67418

5.3 medium SSVC exploitation: none Awaiting Analysis
NVD · CVE.org

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.

Fix

Microsoft's update · Moderate

  • Release Notes — azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0 · build 3.13.7-11

From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-11-01.

Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.

Change history 2

  1. StatusReceived → Awaiting AnalysisNVD modified 2026-10-16 16:00
  2. First seenCVSS 5.3NVD modified 2026-10-14 18:17

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 6