RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI
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 (). 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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-67239
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:06 UTC · Revision 1
Source evidence
RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI
core-osv · Original sourcePublished 25 Sept 2026, 16:13 UTC
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 (). 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.
osv:CVE-2026-67239
Complete source record
{
"id": "d1bd89d17738945270544f0cb3c9821ae778d4277aa759f887aa18cda392aa19",
"url": "https://osv.dev/vulnerability/CVE-2026-67239",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "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 (). 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.",
"evidence": "osv:CVE-2026-67239",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-67239",
"aliases": [
"BIT-rabbitmq-2026-67239",
"CVE-2026-67239",
"GHSA-xm9p-57xv-vxwc"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/rabbitmq/rabbitmq-server",
"type": "GIT",
"events": [
{
"introduced": "95c501fbad76c66156346cf364d158d6e30aa4d9"
},
{
"fixed": "47d6d6457c7d1a440daed643cb7d76bba313e79c"
},
{
"introduced": "1929eeadf9b2bac12c5434fb56884ef27370580e"
},
{
"fixed": "1d284b2d2a1e2f845ad22b0d5ee38ec372d50802"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.9"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.3.0"
},
{
"fixed": "4.3.3"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "47d6d6457c7d1a440daed643cb7d76bba313e79c"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.2.9"
},
{
"range": [
{
"fixed": "1d284b2d2a1e2f845ad22b0d5ee38ec372d50802"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.3.3"
}
]
}
}
],
"versions": [
"v4.2.8",
"v4.3.2",
"v4.2.7",
"v4.3.1",
"v4.2.6",
"v4.3.0",
"v4.2.5",
"v4.2.4",
"v4.2.3",
"v4.2.2",
"v4.2.1",
"v4.2.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-67239.json"
}
}
],
"modified": "2026-10-28T02:30:24.149270362Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9",
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67239.json",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-xm9p-57xv-vxwc",
"https://nvd.nist.gov/vuln/detail/CVE-2026-67239"
],
"provider_metadata": {
"cwe_ids": [
"CWE-79"
],
"cna_assigner": "GitHub_M",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.18"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.23"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.14"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67239.json"
}
},
"related_cves": [
{
"value": "CVE-2026-67239",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490720,
"published_at": "2026-09-25T16:13:29.231+00:00"
}