These pages are published after PatchSiren validates generated defensive summaries against stored public CVE and source evidence.
CVE-2026-67236 is a high-severity vulnerability in RabbitMQ that allows for the recovery of login credentials due to insecure cookie handling. The vulnerability affects RabbitMQ versions 4.2.0 to 4.2.8 and 4.3.2, and an attacker with same-origin cross-site scripting, an HTTP-readable network position, or local access to the browser cookie store could recover the actual login credentials. This issue is fix [truncated]
CVE-2026-67233 debrief: RabbitMQ shovel management resource authorization issue allows monitoring users to delete or restart shovels. The issue arises from the shovel management resource's is_authorized/2 delegates to rabbit_mgmt_util:is_authorized_monitor/2, which accepts the monitoring tag. This allows monitoring users, intended for read-only visibility, to delete or restart any shovel in any vhost they [truncated]
CVE-2026-67404 is a critical vulnerability in RabbitMQ, a messaging and streaming broker. When no CA bundle is available, the ssl_options/1 function falls back to [{verify, verify_none}] with no warning, allowing an attacker in a man-in-the-middle position to forge the JWKS response and lead the broker to accept arbitrary JWTs. This issue is fixed in RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
CVE-2026-67231 is a critical vulnerability in RabbitMQ that allows for TLS client-authentication bypass. An attacker who knows the issuer DN + serial of any whitelisted certificate can connect with a forged self-signed cert. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0. The vulnerability impacts RabbitMQ deployments, potentially allowing unauthorized access. Defenders should a [truncated]
CVE-2026-67228 is a denial-of-service vulnerability in RabbitMQ, a messaging and streaming broker. An authorized policymaker can cause a node to crash by issuing roughly one million requests with distinct component values, exhausting the atom table. This issue is fixed in versions 4.2.7 and 4.3.1. The vulnerability affects RabbitMQ deployments, particularly those with policymaker privileges exposed. Defen [truncated]
CVE-2026-66077 is a high-severity vulnerability in RabbitMQ, a messaging and streaming broker. The management UI uses EJS 1.0, which does not HTML-escape user input, allowing an attacker to embed JavaScript in a TLS client certificate's Subject DN. When an administrator views the connection detail page, the script executes in the admin's browser session, enabling full account takeover.
CVE-2026-66079 is a high-severity vulnerability in RabbitMQ, a messaging and streaming broker. An unauthenticated network attacker can crash any RabbitMQ node with the AMQP 1.0 listener enabled by sending a single ~19-byte frame, causing a denial-of-service (DoS) condition. The vulnerability is due to a flaw in the amqp10_framing:decode_bin/1 function, which allows an attacker to exploit the heap memory, [truncated]
CVE-2026-75516 is a high-severity vulnerability in the RabbitMQ Java client library that could allow a malicious AMQP server or man-in-the-middle attacker to send oversized frames, potentially causing memory exhaustion and client process termination. The vulnerability is caused by the incorrect application of Math.min(maxInboundMessageBodySize, frameMax) after Connection.Tune negotiation. This issue can b [truncated]
A vulnerability in RabbitMQ amqp091-go, a Go AMQP 0.9.1 client, can cause connection stalls, missed heartbeats, deadlocks, and disconnection due to synchronous sending of publisher confirmations and other events to application-provided channels. This issue is fixed in version 1.13.0. The vulnerability is caused by synchronous sending of publisher confirmations, flow-control events, consumer cancellations, [truncated]
A vulnerability in RabbitMQ amqp091-go allows a network attacker to weaken transport protection for AMQP messages and credentials by negotiating an obsolete protocol version when connecting through an amqps URI. This issue is fixed in version 1.13.0. The vulnerability arises from the tlsConfigFromURI function in uri.go, which creates tls.Config values without setting MinVersion to tls.VersionTLS12. As a r [truncated]
A vulnerability in the amqp091-go library can lead to unexpected memory consumption or application-layer denial of service (DoS) when a compromised or malicious AMQP broker forces the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This issue can cause significant disruptions to applications using the vulnerable library, emphasizing the need for [truncated]
CVE-2026-69220 is a denial-of-service vulnerability in the RabbitMQ Java client library. A malicious AMQP server or network intermediary can send a specially crafted pre-authentication connection.start frame to trigger a StackOverflowError, terminating the client input processing thread. This issue is fixed in version 5.33.1. The vulnerability allows a remote attacker to cause a denial-of-service conditio [truncated]
CVE-2026-69219 is a high-severity vulnerability in the RabbitMQ Java client library that allows for denial of service via memory exhaustion. The issue arises from the library's handling of wire-declared content lengths, which can lead to an OutOfMemoryError. This vulnerability is fixed in version 5.33.1. A malicious AMQP peer can exploit this by sending a LongString or byte-array field with type tag S and [truncated]
CVE-2026-63337 debrief based on the supplied source corpus. The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, an attacker can exploit a vulnerability that triggers static initializers of classes already present in the victim JVM, potentially affecting confidentiality, integrity, and availability. Java and JVM-based appl [truncated]
CVE-2026-63336 debrief based on the supplied source corpus. The RabbitMQ Java client library prior to version 5.33.0 has a vulnerability that allows arbitrary server certificates, including self-signed certificates, to be accepted. This causes a network attacker to impersonate the RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname validation. Defenders respons [truncated]
A vulnerability in the RabbitMQ Java client library allows a malicious broker peer to send a malformed AMQP sequence, causing a denial of service for work using the affected connection. This issue is fixed in version 5.31.0. The vulnerability is caused by the CommandAssembler.consumeBodyFrame method subtracting the peer-controlled payload length before validating that it fits, driving remainingBodyBytes n [truncated]
CVE-2026-61634 RabbitMQ Java client library vulnerability allows for denial of service via malicious AMQP frame payloads. The issue is fixed in version 5.33.0. This vulnerability affects RabbitMQ Java client library deployments, allowing a malicious or compromised broker to send a method frame larger than the negotiated frame_max, causing a denial of service. Defenders should assess exposure and prioritiz [truncated]
CVE-2026-57221 is a RabbitMQ vulnerability allowing enumeration of queue and exchange names and reading of queue message and consumer counts due to lack of authorization checks on passive queue.declare and exchange.declare AMQP 0-9-1 operations. This issue affects RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users of these versions should apply patches to prevent queue and exchange enume [truncated]
CVE-2026-57220 is a HIGH severity vulnerability in RabbitMQ stream listener allowing unauthenticated remote clients to declare oversized frame lengths and consume broker memory. This issue is fixed in version 4.2.6. Users of RabbitMQ versions prior to 4.2.6 should apply the patch to prevent potential denial of service attacks. The vulnerability impacts RabbitMQ deployments, particularly those with publicl [truncated]
CVE-2026-57219 is a high-severity vulnerability in RabbitMQ that discloses OAuth 2 client secrets to unauthenticated callers when the management plugin and OAuth configuration are enabled. The issue arises from the obsolete GET /api/auth endpoint's ability to expose credentials. This vulnerability has a CVSS score of 8.7 and is classified as HIGH. Users of RabbitMQ, especially those with management plugin [truncated]
RabbitMQ is a messaging and streaming broker that had a vulnerability in its AMQP 0-9-1 implementation. Prior to version 4.2.6, an existing consumer could continue receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes. This occurred because existing consumers were not properly canceled or reauthorized at delivery time after channel user state changes. The issue [truncated]
CVE-2026-57217 is a high-severity vulnerability in RabbitMQ that allows restricted topic writes and binds during metadata-store failures. The issue arises from topic-permission lookup errors from Khepri collapsing to undefined, which the internal backend treats as allow. This vulnerability is fixed in RabbitMQ versions 3.13.15, 4.0.21, 4.1.11, and 4.2.6. The vulnerability has a high severity score of 7 an [truncated]
CVE-2026-57216 is a medium-severity vulnerability in RabbitMQ that allows for authentication bypass under certain conditions involving PROXY-protocol paths and loopback-bound listeners. The issue arises from the way RabbitMQ handles authentication for AMQP 0-9-1, AMQP 1.0, and Stream Protocol, specifically using listener-side socket addresses instead of the real client source. This allows loopback-restric [truncated]
CVE-2026-57215 is a high-severity vulnerability in RabbitMQ that allows foreign bindings to amq.rabbitmq.reply-to destinations. This issue is fixed in RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. The vulnerability is caused by volatile direct-reply-to queues being accepted at bind and route time but missing from Khepri-backed deletion checks, leaving persistent route entries after unbind. Users o [truncated]
CVE-2026-57214 is a high-severity vulnerability in RabbitMQ's management UI. Prior to version 4.2.5, the UI renders the x-internal-purpose queue or exchange argument into an HTML title attribute without proper escaping on the Queues and Exchanges pages. This allows a user with permission to declare a queue or exchange to execute JavaScript in another user's browser. The issue is fixed in version 4.2.5. Th [truncated]
CVE-2026-57213 is a medium-severity vulnerability in RabbitMQ's federation management plugin. Prior to versions 3.13.14, 4.0.19, 4.1.10, and 4.2.5, the plugin does not properly escape the consumer_tag field on the Federation Status page, allowing a user with configuration privileges to inject JavaScript code. This code would be executed in the browser of users viewing the page. The vulnerability has a CVS [truncated]
CVE-2026-57212 is a high-severity vulnerability in RabbitMQ's management HTTP API, allowing potential denial-of-service attacks via oversized JSON bodies. The issue exists in versions prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5. Users should upgrade to a patched version to mitigate this issue. The vulnerability arises from inadequate size checks in the rabbitmq_management HTTP API, specifically in the rea [truncated]
CVE-2026-57211 is a vulnerability in the RabbitMQ management plugin static file handler rabbit_mgmt_wm_static. Prior to versions 4.1.11 and 4.2.6 on Windows, with multiple management extension plugins enabled, URL-encoded backslashes can be passed to erl_prim_loader:read_file_info before path validation. This can cause outbound DNS and SMB requests to attacker-controlled UNC paths. The issue is fixed in v [truncated]
A medium-severity vulnerability in RabbitMQ messaging and streaming broker affects versions from 3.7.0 through 4.1.1 and 4.0.12. The issue, classified as CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), has been addressed in versions 4.1.2 and 4.0.13. The CVSS 4.0 vector indicates network attack vector with high attack complexity, requiring high privileges and user interaction, [truncated]
A regex injection vulnerability in RabbitMQ's MQTT plugin allows authenticated users to bypass topic-level authorization controls. The flaw exists in versions 4.2.0 through 4.2.3, where user-supplied client_id values from MQTT CONNECT packets are substituted into authorization regex patterns without proper escaping of special regex characters. An attacker can craft a malicious client_id containing regex m [truncated]