Skip to content
COOEY

EXPOSURES › CVE-2026-67231

CVE-2026-67231

CRITICAL
DETAIL
SourceNVD · cve Published2026-09-23 CVSS9.1 Referencehttps://nvd.nist.gov/vuln/detail/CVE-2026-67231 ↗
SHAME 65/100 unpatchedexploited-in-wild

CVE-2026-67231 allows TLS client-authentication bypass in RabbitMQ via a flawed certificate whitelist check.

RabbitMQ's trust-store plugin incorrectly validates certificates by matching issuer name and serial number instead of cryptographic material, enabling attackers to forge self-signed certificates if they know the issuer and serial. DIB orgs must patch to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, or 4.3.0 and disable the plugin if unpatched, as this flaw could allow unauthorized access to messaging systems.

Shame score — A critical TLS bypass flaw in a widely used messaging broker that relies on non-cryptographic certificate fields for validation, exposing systems to unauthorized access if the plugin is enabled.

▸ RECOMMENDED ACTION  Critical severity — schedule patching of the affected products.

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.

AFFECTED FEDRAMP PRODUCTS · 4
PRODUCTSTATUS
Clarity
Broadcom
Authorized
General Support Systems (GSS)
Broadcom
Authorized
Rally
Broadcom
Authorized
Symantec Gov Cloud Security (GCS)
Broadcom
In Process