CVE-2026-67231
Last modified
CVE-2026-67231 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| rabbitmq | rabbitmq-server | >= 3.13.0, < 3.13.15; >= 4.0.0, < 4.0.20; >= 4.1.0, < 4.1.11; >= 4.2.0, < 4.2.6 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-67231?
How severe is CVE-2026-67231?
How do I fix CVE-2026-67231?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-67225RabbitMQ is a messaging and streaming broker. From 3.13.0 un…6.3
- CVE-2026-67226RabbitMQ is a messaging and streaming broker. From 4.0.0 unt…6.9
- CVE-2026-67227RabbitMQ is a messaging and streaming broker. From 4.0.0 unt…5.9
- CVE-2026-67228RabbitMQ is a messaging and streaming broker. Prior to versi…6.9
- CVE-2026-67229RabbitMQ is a messaging and streaming broker. Prior to versi…6.9
- CVE-2026-67230RabbitMQ is a messaging and streaming broker. From 3.13.0 un…6.3
- CVE-2026-67232RabbitMQ is a messaging and streaming broker. Prior to versi…8.2
- CVE-2026-67233RabbitMQ is a messaging and streaming broker. Prior to versi…6
- CVE-2026-67234RabbitMQ is a messaging and streaming broker. From 4.2.0 unt…2.3
- CVE-2026-67235RabbitMQ is a messaging and streaming broker. Prior to versi…7.1
- CVE-2026-67236RabbitMQ is a messaging and streaming broker. From 4.2.0 unt…8.2
- CVE-2026-67237RabbitMQ is a messaging and streaming broker. From 4.2.0 unt…7.5
Are you affected by CVE-2026-67231?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
