BIT-rabbitmq-2026-67239
See a problem?- Import Source
- https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-67239.json
- JSON Data
- https://api.osv.dev/v1/vulns/BIT-rabbitmq-2026-67239
- Aliases
-
- CVE-2026-67239
- GHSA-xm9p-57xv-vxwc
- Published
- 2026-10-01T09:33:36Z
- Modified
- 2026-10-01T10:10:50Z
- Summary
- RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI
- Details
-
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.
- Database specific
{ "cpes": [ "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*" ], "severity": "High" }- References
Affected packages
Bitnami / rabbitmq
Package
- Name
- rabbitmq
- Purl
- pkg:bitnami/rabbitmq
Severity
- 7.6 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X CVSS Calculator