{"id":"CVE-2026-67231","revision":"6df8a6c96ae649dfac3358e79d050a76","records":[{"revision":"6df8a6c96ae649dfac3358e79d050a76","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-67231","aliases":[],"title":"RabbitMQ: Trust-store whitelist by Issuer+Serial only","description":"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.","state":0,"publishedAt":"2026-09-23T20:47:36.045+00:00","modifiedAt":"2026-09-29T02:18:07.983+00:00","affected":[{"ecosystem":"Vendor product","name":"rabbitmq-server","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"rabbitmq\",\n                    \"product\": \"rabbitmq-server\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 3.13.0, < 3.13.15\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 4.0.0, < 4.0.20\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 4.1.0, < 4.1.11\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 4.2.0, < 4.2.6\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","vector":"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","score":9.1,"severity":"CRITICAL"}],"references":["https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-cw8c-4m83-9c6w","https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6","https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-67231","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-67231","identifiers":["CVE-2026-67231"]},"retained":false,"historicalAffected":[]}],"coverage":[]}