These pages are published after PatchSiren validates generated defensive summaries against stored public CVE and source evidence.
CVE-2026-107386 debrief based on the supplied source corpus. The CVE record was published on 2026-10-08T18:54:12.465Z and has not been modified since then. This vulnerability affects amqp091-go, allowing a malicious AMQP peer to cause memory pressure or out-of-memory termination before authentication completes. Versions between 1.13.0 and 1.14.0 are affected, and upgrading to 1.14.0 or later is recommende [truncated]
A single AMQP message with malformed UTF-8 in a shortstr property can permanently disable a Java client RPC consumer in RabbitMQ. The client decodes malformed bytes into U+FFFD replacement characters, which re-encodes to 3 bytes, exceeding the 255-byte shortstr limit. When the application echoes that value back, as the documented RPC pattern does, the encoder throws an unchecked `IllegalArgumentException` [truncated]
CVE-2026-106123: The RabbitMQ Java client library contains a vulnerability where plaintext broker credentials are leaked in exception messages during property-file/Map-based ConnectionFactory setup. This occurs when parsing the 'uri' key fails, causing the raw connection string, including the username and password, to be concatenated into the exception message. The affected code is located in ConnectionFa [truncated]
CVE-2026-67421 RabbitMQ Management UI vulnerability allows for authorization header redirect. Fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5. The vulnerability exists in RabbitMQ Management UI when OAuth management UI is enabled. An attacker with queue configure permission and a management administrator who can see but not read the queue can exploit this issue, potentially leading to authori [truncated]
RabbitMQ OAuth credential refresh retains revoked runtime tags, allowing a connection to publish messages with a foreign AMQP userid after privileges should have been revoked. This issue affects RabbitMQ versions 3.13.0 through 3.13.18, 4.0.0 through 4.0.23, 4.1.0 through 4.1.14, 4.2.0 through 4.2.9, and 4.3.0 through 4.3.4. The vulnerability is limited to connections that once held impersonator and succe [truncated]
RabbitMQ is vulnerable to a denial-of-service attack. An authenticated user can bind a queue to a topic exchange and publish to it, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This issue arises from the lack of memoization in RabbitMQ's topic matchers, allowing an attacker to exploit this weakness without authentication. The vulnerability is fixed in Rabbit [truncated]
CVE-2026-67415 is a RabbitMQ vulnerability allowing an attacker with specific permissions to cause a denial of service by exhausting the node-wide atom table. This issue is fixed in RabbitMQ versions 4.2.9 and 4.3.3. The vulnerability affects RabbitMQ instances with the management and policymaker tags enabled, and defenders should prioritize patching to prevent potential denial-of-service attacks. The Sho [truncated]
CVE-2026-67413 RabbitMQ denial of service via rabbitmq_jms_topic_exchange plugin. An authenticated tenant can bind and publish to consume broker scheduler CPU and deny service with pathological selectors. This issue affects RabbitMQ versions 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, and 4.3.0 to 4.3.2. Defenders should verify RabbitMQ versions and restrict access to authenticated tenants to mitiga [truncated]
CVE-2026-67412 is a vulnerability in RabbitMQ that allows for cross-vhost message access. A policymaker on one vhost can read and drain messages from another vhost they have no permission on. This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, 4.0.24, and 3.13.18. The vulnerability allows unauthorized message access and deletion with default ack-mode. Defenders should prioritize patching RabbitMQ instan [truncated]
CVE-2026-67411 is a medium-severity vulnerability in RabbitMQ that allows an attacker with valid loopback-restricted account credentials to bypass source-address restrictions when accessing the server through a trusted PROXY Protocol frontend. The vulnerability affects RabbitMQ versions 3.13.0-3.13.18, 4.0.0-4.0.23, 4.1.0-4.1.14, 4.2.0-4.2.9, and 4.3.0-4.3.3. Defenders should prioritize verifying exposure [truncated]
CVE-2026-67410 is a high-severity vulnerability in RabbitMQ that exposes the OAuth2 client secret via an unauthenticated JavaScript endpoint. The issue affects RabbitMQ versions 4.2.0 to 4.3.3 and 4.2.9. An attacker can retrieve the OAuth2 client secret without authentication, potentially leading to token theft and client impersonation. This vulnerability can be exploited by any user who can reach the man [truncated]
A vulnerability in RabbitMQ's JWKS key fetching mechanism allows for a persistent authentication denial of service (DoS) via HTTP response status code ignorance. This issue affects RabbitMQ versions from 3.13.0 until 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18. The vulnerability is caused by the uaajwt.erl module ignoring HTTP response status codes when fetching JWKS keys, leading to potential DoS via key d [truncated]
A low-privileged management user can cause a denial-of-service in RabbitMQ versions 4.1.0-4.3.2, 4.2.8, and 4.1.10 by sending a specially crafted HTTP PUT request to the /api/stream/super-streams/{vhost}/{name} endpoint. This issue allows an authenticated low-privileged management user to cause large transient allocations before the resource permission check, potentially leading to a denial-of-service in [truncated]
The CVE-2026-67407 vulnerability affects RabbitMQ, a messaging and streaming broker, specifically in versions 4.0.0 through 4.3.2, 4.2.8, 4.1.13, and 4.0.22. This medium-severity issue allows a low-privileged authenticated MQTT user to potentially bypass topic authorization when templates embed {clientid} in a [...] character class. Defenders should assess exposure and prioritize patching to prevent poten [truncated]
RabbitMQ messaging and streaming broker has a vulnerability in Shovel component where unencrypted credentials can be exposed in crash dump files due to lack of formatting in state logged by the crash reporter. The issue arises from the Shovel worker genserver processes not implementing the formatstatus/2 callback, leading to the OTP SASL error handler writing full process states, including plaintext AMQP [truncated]
RabbitMQ OAuth2 token expiry check bypass vulnerability allows an attacker to bypass token expiry validation checks, potentially leading to unauthorized access. The vulnerability exists in RabbitMQ versions 4.2.0 to 4.2.8 and 4.3.2, where the OAuth2 token expiry check is bypassed due to incorrect handling of float exp values. RabbitMQ administrators and users with OAuth2 backend enabled should verify and [truncated]
RabbitMQ messaging and streaming broker has a vulnerability in versions 4.2.0 through 4.2.8 and 4.3.2. An AMQP 1.0 management exchange.declare skips alternate-exchange permission checks, allowing users with configure permissions on an exchange to route unroutable messages into an alternate exchange they lack write permissions for. This issue can lead to unauthorized message routing. The vulnerability is f [truncated]
CVE-2026-67239 is a high-severity vulnerability in RabbitMQ, a messaging and streaming broker. An attacker can exploit this vulnerability to conduct Stored Cross-Site Scripting (XSS) attacks via TLS peer-certificate DN in the stream-management UI. This requires a non-default configuration: a stream TLS listener with 'verifypeer' and an attacker-obtainable trusted certificate with a malicious Distinguished Name (DN).
CVE-2026-67237 RabbitMQ JavaScript Injection. RabbitMQ versions 4.2.0 to 4.2.8 and 4.3.2 are vulnerable to JavaScript injection via the management UI. This issue arises from set_token_auth/2 inserting a bearer token from the Authorization header or access_token cookie into OAuth bootstrap JavaScript without proper escaping. The vulnerability allows attacker-controlled token content to execute JavaScript i [truncated]
CVE-2026-67234 is a low-severity vulnerability affecting RabbitMQ, a messaging and streaming broker. The issue arises from the improper handling of authentication mechanism preferences, leading to non-ASCII cookie names that violate RFC 6265. This can cause problems with browser preference deletion across logout and login cycles. The vulnerability is fixed in RabbitMQ versions 4.2.8 and 4.3.2.
CVE-2026-67230 is a vulnerability in RabbitMQ, a messaging and streaming broker, affecting versions 3.13.0 through 3.13.15, 4.0.20, 4.1.11, and 4.2.6 when the rabbitmq_web_stomp plugin is enabled. An unauthenticated client can maintain a connection with a slow stream of small frames, accumulating unbounded pre-authentication state. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
RabbitMQ is vulnerable to atom exhaustion through the /api/global-parameters/:name endpoint, which can be exploited by a policymaker user to crash the node. This issue arises from the toatom/1 function using binarytoatom/2, an unsafe operation. Affected versions include 4.0.0 through 4.0.21, 4.1.0 through 4.1.13, 4.2.0 through 4.2.6, and 4.3.0. The vulnerability requires the policymaker tag, not the manag [truncated]
RabbitMQ is vulnerable to an admin-only atom exhaustion issue via a PUT /api/users tags list request. A malicious administrator can create a user with approximately 1 million unique tags to crash a node in a single request. This issue is fixed in RabbitMQ versions 4.0.22, 4.1.14, and 4.2.7. The vulnerability allows an administrator to create a user with a large number of unique tags, causing an atom exhau [truncated]
A vulnerability in RabbitMQ, a messaging and streaming broker, allows a remote client to cause excessive memory pressure and denial of service by declaring an oversized frame when the stream plugin is enabled. This issue affects versions from 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6. The vulnerability can lead to denial of service attacks, impacting the availability of messaging and streaming servi [truncated]
RabbitMQ is vulnerable to LDAP injection due to insufficient DN escaping in the rabbitmq_auth_backend_ldap plugin. A crafted username can alter the LDAP bind DN, potentially selecting a different directory entry. This issue affects RabbitMQ 3.13, 4.0, 4.1, 4.2, and 4.3 maintenance lines. However, conflicting information exists regarding the first fixed versions for 3.13, 4.0, and 4.1 lines.
CVE-2026-67222 is a vulnerability in RabbitMQ, a messaging and streaming broker. Affected versions are 3.13.0 through 3.13.15, 4.0.20, 4.1.11, and 4.2.6. The issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. This vulnerability can cause node crashes and Erlang VM atom exhaustion due to mechanisms/1 applying list_to_atom/1 to every colon-delimited token in an attacker-controlled auth_mechanism [truncated]
CVE-2026-66078 is a vulnerability in RabbitMQ that allows an administrator to bypass a safeguard and delete protected-tagged service accounts via the bulk endpoint. This issue arises from the lack of a protected-tag check in the rabbitauthbackendinternal:deleteuser/2 function. The vulnerability is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. A RabbitMQ administrator can exploit this vulnerability [truncated]
RabbitMQ messaging and streaming broker is vulnerable to Atom table exhaustion via the management API node field. The issue exists in versions 3.13.0 through 3.13.15, 4.0.20, 4.1.11, and 4.2.6. An attacker with the management tag and one vhost can cause a crash by making roughly 900K requests, affecting all tenants and users with the lowest privilege.
RabbitMQ is vulnerable to atom exhaustion through OAuth2 JWT tag scope values. This issue is fixed in versions 3.13.15, 4.0.22, 4.1.11, 4.2.6, and 4.3.1. The vulnerability allows for potential denial of service through atom exhaustion. Defenders managing RabbitMQ deployments should assess exposure and prioritize updates, especially in configurations where user-influenced scopes are present in IdP-issued J [truncated]
CVE-2026-61837 debrief based on the supplied source corpus. The CVE record was published on 2026-09-25T17:17:09.810Z and has not been modified since then. RabbitMQ is a messaging and streaming broker that had a vulnerability from versions 4.0.0 until 4.3.3, 4.2.9, 4.1.14, and 4.0.23. The AMQP 1.0 management GET /bindings endpoint exposed full binding topology to any authenticated AMQP user without resourc [truncated]
