CVE-2026-67239: RabbitMQ is a messaging and streaming broker.
Medium CVSS 5.4
- CVE id
- CVE-2026-67239
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| RabbitMQ Runtimes and servers |
>= 3.13.0, < 3.13.18 >= 4.0.0, < 4.0.23 >= 4.1.0, < 4.1.14 >= 4.2.0, < 4.2.9 >= 4.3.0, < 4.3.3 |
3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3 |
How to fix it
Upgrade RabbitMQ to the fixed release of the line you run: 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3.
rabbitmqctl version
- Upgrade RabbitMQ (the rabbitmq image tag or the rabbitmq-server package) to the patched release, node by node.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
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.
References
- CVE-2026-67239 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-67239
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-xm9p-57xv-vxwc
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.