{"published_count":667,"discovered_count":673,"count":5,"cves":[{"cve_id":"CVE-2026-67419","title":"CPU exhaustion in topic exchange routing via bindings with consecutive # wildcards","description":"An authenticated user who can bind a queue to a topic exchange and publish to\nthat exchange can force the routing engine into combinatorial recursion by using\na binding key that contains **consecutive `#` segments**.\n\nWhen such a binding is matched against a routing key of comparable depth, the\nmatcher repeatedly re-enters identical `{trie node, remaining routing-key\nsuffix}` states without memoization, and builds a duplicate list of destination\nresults that is only deduplicated **after** the full traversal completes.\n\nA binding and routing key only tens of bytes long can therefore drive millions\nto billions of recursive matcher invocations and allocate a correspondingly\nlarge intermediate result list, all while producing exactly **one** queue\ndelivery. The work is performed inline in the routing path with no connection,\nchannel, queue, message-size, or memory-alarm limit interrupting a single\nin-progress traversal.","severity":"high","cvss_score":7.1,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","cwe":"CWE-407","product":"RabbitMQ","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-67419","published":"2026-08-18"},{"cve_id":"CVE-2026-67418","title":"Inapplicable PUBLISH property disconnects matching subscribers","description":"RabbitMQ's MQTT 5 property parser accepts properties without checking whether\nthey are valid for the enclosing packet type. An authenticated publisher can\ninclude `Request-Problem-Information` (MQTT property 0x17) in a `PUBLISH` —\na property that the MQTT 5 specification restricts to `CONNECT` — and the\nbroker will store and route it.\n\nWhen a matching subscriber's reader later serializes the outbound `PUBLISH`,\n`serialise_prop/2` has **no clause** for `Request-Problem-Information`, raising\n`error:function_clause`. That exception is not contained at the victim\nqueue-event boundary, so the **victim's entire MQTT connection** is closed.\nThe publisher's connection and the broker remain healthy.","severity":"medium","cvss_score":5.3,"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","cwe":"CWE-20","product":"RabbitMQ","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-67418","published":"2026-08-18"},{"cve_id":"CVE-2026-67416","title":"Descriptor prefix collision in the AMQP 1.0 parser lets stored messages crash consumers","description":"RabbitMQ is an open source multi-protocol messaging broker. The optimized AMQP 1.0 server-mode parser recognizes symbolic message body descriptors by matching a fixed textual prefix without validating the encoded symbol length, so an authenticated publisher with write permission to an exchange or queue can submit a described value whose descriptor merely begins with `amqp:data:binary`, `amqp:amqp-sequence:list`, or `amqp:amqp-value:*` (for example the well-formed but unknown descriptor `amqp:data:binary@`) and have it misclassified as a standard body section. The accepted bytes are retained unchanged through classic, quorum, and stream queues and forwarded to AMQP 1.0 consumers, whose strict decoders reject the unknown descriptor; conversion to AMQP 0-9-1 and other protocols performs a full decode on the broker side, causing an uncontrolled parser exit in the consumer protocol process. With acknowledgement-required consumers the stored poison entry can be repeatedly redelivered after reconnection, resulting in denial of service of consumer sessions or channels (the broker node itself remains alive). Fixed in RabbitMQ 4.3.4, 4.2.10, 4.1.15, and 4.0.24, which require exact symbolic descriptor lengths in the fast-path parsing clauses.","severity":"medium","cvss_score":5.3,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:L","cwe":"CWE-20","product":"RabbitMQ","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-67416","published":"2026-08-07"},{"cve_id":"CVE-2026-67421","title":"Stored HTML injection in the management UI OAuth error handling leading to credential theft","description":"RabbitMQ Management renders an AMQP authorization-error reason as HTML when the OAuth management UI is enabled. A user who can configure a queue can place an HTML `<base>` element in the queue name. If a management administrator who can see that queue but lacks AMQP read permission clicks **Get Message(s)**, the queue name is returned in an `ACCESS_REFUSED` reason and inserted into the page without HTML escaping.\n\nThe default Content Security Policy blocks inline script execution in the current source, but it does not define `base-uri` or `connect-src`. An injected `<base>` element can therefore change the document base URL. The next automatic relative management API refresh is sent to an attacker-controlled CORS endpoint with the victim's explicit `Authorization` header.\n\nThe result is theft of a management administrator's Basic or Bearer credential and subsequent control of RabbitMQ through the management API. The demonstrated chain does not provide broker-host code execution or arbitrary file access.","severity":"medium","cvss_score":4.5,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N","cwe":"CWE-79","product":"RabbitMQ","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-67421","published":"2026-08-18"},{"cve_id":"CVE-2026-67420","title":"OAuth credential refresh retains revoked runtime tags","description":"When an existing AMQP connection refreshes from an OAuth token that grants the\n`impersonator` tag to a valid same-username token that **no longer** grants that\ntag, RabbitMQ updates the OAuth backend implementation (token/scopes/expiry) but\nleaves the connection's runtime `#user.tags` unchanged.\n\n`rabbit_access_control:check_user_id/2` then still honors the stale\n`impersonator` tag, so the connection (including newly opened channels) can\ncontinue publishing messages with a foreign AMQP `user_id` after that privilege\nshould have been revoked.\n\nA fresh connection using the downgraded token correctly refuses the same\npublish, proving the defect is stale session state rather than the token itself.","severity":"low","cvss_score":2.3,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","cwe":"CWE-613","product":"RabbitMQ","reference_count":1,"url":"https://www.cve.org/CVERecord?id=CVE-2026-67420","published":"2026-08-18"}]}