RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI

Summary

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18 and 4.0.23 and 4.1.14 and 4.2.9 and 4.3.3, Stored XSS via TLS peer-certificate DN in stream-management UI (sibling of V-11). lines 102/106/110 render peercertsubject / peercertissuer with raw <%= %> and no fmtstring(). RFC4514 backslash-escaping of </> is HTML-inert and bypassable (<img ... //>). Requires non-default config: a stream TLS listener with verifypeer and an attacker-obtainable trusted cert with a malicious Same as the connection.ejs finding, against operators viewing the stream-connection detail rabbitmqstream + rabbitmqstreammanagement enabled with a TLS listener using verifypeer Attacker can obtain a certificate signed by a CA the listener trusts, with attacker-chosen DN An operator views the. This issue is fixed in versions 3.13.18 and 4.0.23 and 4.1.14 and 4.2.9 and 4.3.3.

Timeline

1. Sep 25, 2026, 4:13 PM UTCCVE published
2. Sep 25, 2026, 4:44 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Sep 25, 2026, 4:44 PM UTCRecord last updated

Affected versions

• rabbitmq rabbitmq-server

  From 3.13.0 · fixed in 3.13.18; From 4.0.0 · fixed in 4.0.23; From 4.1.0 · fixed in 4.1.14; From 4.2.0 · fixed in 4.2.9; From 4.3.0 · fixed in 4.3.3

• rabbitmqBitnami

  From 3.13.0 · fixed in 3.13.18; From 4.0.0 · fixed in 4.0.23; From 4.1.0 · fixed in 4.1.14; From 4.2.0 · fixed in 4.2.9; From 4.3.0 · fixed in 4.3.3

References 3