RabbitMQ: Trust-store whitelist by Issuer+Serial only
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, The trust-store plugin installs a verify_fun that overrides {bad_cert, unknown_ca} / {bad_cert, selfsigned_peer} when the presented cert "matches" a whitelisted one. The match key is extract_issuer_id/1 → public_key:pkix_issuer_id/2 → {IssuerName, SerialNumber} , both fields are taken verbatim from the presented certificate body and contain no public-key, SKI, fingerprint or signature material. is_whitelisted/1 is a pure ets:member lookup; the stored full DER is used only for list/0 display and is never compared against the presented cert. cacerts is [], so the whitelisted cert is never used as a trust anchor for path validation either. TLS client-authentication bypass: an attacker who knows the issuer DN + serial of any whitelisted certificate can connect with a forged self-signed cert. Preconditions include rabbitmq_trust_store plugin enabled and used as the TLS verify_fun Attacker knows or can guess the {Issuer, Serial} of at least one whitelisted cert (non-secret; exposed via CLI/logs/any cert copy). This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-67231
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 01:58 UTC · Revision 1
Source evidence
RabbitMQ: Trust-store whitelist by Issuer+Serial only
core-osv · Original sourcePublished 23 Sept 2026, 20:47 UTC
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, The trust-store plugin installs a verify_fun that overrides {bad_cert, unknown_ca} / {bad_cert, selfsigned_peer} when the presented cert "matches" a whitelisted one. The match key is extract_issuer_id/1 → public_key:pkix_issuer_id/2 → {IssuerName, SerialNumber} , both fields are taken verbatim from the presented certificate body and contain no public-key, SKI, fingerprint or signature material. is_whitelisted/1 is a pure ets:member lookup; the stored full DER is used only for list/0 display and is never compared against the presented cert. cacerts is [], so the whitelisted cert is never used as a trust anchor for path validation either. TLS client-authentication bypass: an attacker who knows the issuer DN + serial of any whitelisted certificate can connect with a forged self-signed cert. Preconditions include rabbitmq_trust_store plugin enabled and used as the TLS verify_fun Attacker knows or can guess the {Issuer, Serial} of at least one whitelisted cert (non-secret; exposed via CLI/logs/any cert copy). This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
osv:CVE-2026-67231
Complete source record
{
"id": "cc8e6b7893d08900768a7a997838ea0f6eda94b8090b5b49aeb786f78927d926",
"url": "https://osv.dev/vulnerability/CVE-2026-67231",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ: Trust-store whitelist by Issuer+Serial only",
"summary": "RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, The trust-store plugin installs a verify_fun that overrides {bad_cert, unknown_ca} / {bad_cert, selfsigned_peer} when the presented cert \"matches\" a whitelisted one. The match key is extract_issuer_id/1 → public_key:pkix_issuer_id/2 → {IssuerName, SerialNumber} , both fields are taken verbatim from the presented certificate body and contain no public-key, SKI, fingerprint or signature material. is_whitelisted/1 is a pure ets:member lookup; the stored full DER is used only for list/0 display and is never compared against the presented cert. cacerts is [], so the whitelisted cert is never used as a trust anchor for path validation either. TLS client-authentication bypass: an attacker who knows the issuer DN + serial of any whitelisted certificate can connect with a forged self-signed cert. Preconditions include rabbitmq_trust_store plugin enabled and used as the TLS verify_fun Attacker knows or can guess the {Issuer, Serial} of at least one whitelisted cert (non-secret; exposed via CLI/logs/any cert copy). This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.",
"evidence": "osv:CVE-2026-67231",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-67231",
"aliases": [
"BIT-rabbitmq-2026-67231",
"CVE-2026-67231",
"GHSA-cw8c-4m83-9c6w"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/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": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
},
{
"fixed": "1929eeadf9b2bac12c5434fb56884ef27370580e"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.6"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.2.6"
},
{
"range": [
{
"fixed": "1929eeadf9b2bac12c5434fb56884ef27370580e"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.3.0"
}
]
}
}
],
"versions": [
"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-67231.json"
}
}
],
"modified": "2026-10-28T02:30:48.854493641Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6",
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67231.json",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-cw8c-4m83-9c6w",
"https://nvd.nist.gov/vuln/detail/CVE-2026-67231"
],
"provider_metadata": {
"cwe_ids": [
"CWE-295"
],
"cna_assigner": "GitHub_M",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.15"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.20"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.11"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67231.json"
}
},
"related_cves": [
{
"value": "CVE-2026-67231",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517173,
"published_at": "2026-09-23T20:47:36.045+00:00"
}