CVE-2026-66077: RabbitMQ is a messaging and streaming broker.
Medium CVSS 6.1
- CVE id
- CVE-2026-66077
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| RabbitMQ Runtimes and servers |
>= 3.13.0, < 3.13.15 >= 4.0.0, < 4.0.20 >= 4.1.0, < 4.1.11 >= 4.2.0, < 4.2.6 |
3.13.15, 4.0.20, 4.1.11, 4.2.6 |
How to fix it
Upgrade RabbitMQ to the fixed release of the line you run: 3.13.15, 4.0.20, 4.1.11, 4.2.6.
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. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, The management UI uses EJS 1.0 in which <%= ... %> does NOT HTML-escape. connection.ejs:135 renders <%= connection.ssldetails.peercertsubject %> (and peercertissuer) directly into the page. The same pattern appears in streamConnection.ejs:102,106,110. The values come from rabbitssl:peercertsubject/1 which formats the DN as a string without HTML escaping. The verifier corrected the original researcher's claim: this is reachable only when the listener is configured with verifypeer (so the certificate must be signed by a CA in the broker's trust store, not arbitrary self-signed); however, in deployments using mTLS for client authentication, any user who can request a certificate from the organisational CA controls the Subject CN. An attacker who can obtain a TLS client certificate signed by a CA the broker trusts (with verifypeer enabled) can embed JavaScript in the certificate's Subject DN. When any administrator views that connection in the management UI, the script executes in the admin's browser session, allowing full account takeover (create users, export definitions, etc.). The management UI's CSP includes 'unsafe-inline', so inline script execution is not blocked. Preconditions include TLS listener configured with ssloptions.verify = verifypeer Attacker can obtain a CA-signed client certificate with attacker-chosen Subject (e.g. self-service corporate PKI, or rabbitmqtruststore plugin in use) Administrator views the connection detail page. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
References
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.