cve.bz

CVE-2026-67239 broadcom rabbitmq server: Cross-site Scripting

7.6 highEPSS 0.2%

High (7.6) in broadcom rabbitmq server. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.6 high
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

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67239 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67239?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67239?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67239 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
broadcom:rabbitmq_serverfrom 3.13.0 before 3.13.18
broadcom:rabbitmq_serverfrom 4.0.0 before 4.0.23
broadcom:rabbitmq_serverfrom 4.1.0 before 4.1.14
broadcom:rabbitmq_serverfrom 4.2.0 before 4.2.9
broadcom:rabbitmq_serverfrom 4.3.0 before 4.3.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13rabbitmq-serverno fix listedDEBIAN-CVE-2026-67239
Debian14rabbitmq-server4.3.6-1DEBIAN-CVE-2026-67239
Ubuntu22.04:LTSrabbitmq-server3.9.27-0ubuntu0.6UBUNTU-CVE-2026-67239 USN-8933-1
Ubuntu24.04:LTSrabbitmq-server3.12.1-1ubuntu1.7UBUNTU-CVE-2026-67239 USN-8933-1
Ubuntu26.04:LTSrabbitmq-server4.0.5-10ubuntu5.2UBUNTU-CVE-2026-67239 USN-8933-1
Ubuntu26.10rabbitmq-serverno fix listedUBUNTU-CVE-2026-67239
UbuntuPro:16.04:LTSrabbitmq-server3.5.7-1ubuntu0.16.04.4+esm3UBUNTU-CVE-2026-67239 USN-8933-1
UbuntuPro:18.04:LTSrabbitmq-server3.6.10-1ubuntu0.5+esm1UBUNTU-CVE-2026-67239 USN-8933-1
UbuntuPro:20.04:LTSrabbitmq-server3.8.3-0ubuntu0.3+esm2UBUNTU-CVE-2026-67239 USN-8933-1
Red Hathummingbird:1rabbitmq-server4.30:4.3.6-1.hum1RHSA-2026:67552
Azure Linux3rabbitmq-server3.13.7-10AZL-105756

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is evaluated as having Moderate severity by Red Hat because exploitation demands significant prerequisites: both stream and stream-management plugins must be enabled, mutual TLS with client certificate verification must be active, and the attacker must hold a certificate signed by a trusted certificate authority. These features are not enabled concurrently in standard deployments. Furthermore, successful execution requires an administrator to actively inspect the specific stream connection details in the web interface, substantially reducing the likelihood of exposure.

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.6-1.hum1Fixed 2026-09-15RHSA-2026:67552
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 16.2rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 17.1rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 18.0rabbitmq-serverFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67239.

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON