Skip to content
major vulnerability· requires attention

RabbitMQ is widely used messaging infrastructure; this auth bypass lets attackers authenticate to brokers, risking broad disruption and data interception across organizations.

Applications

CVE-2026-67231

9.1
Critical
EPSS 0.25%Patch availableSep 24, 2026

RabbitMQ trust-store plugin allows TLS client-auth bypass via forged certificates

common questions

Is CVE-2026-67231 being exploited?

Not confirmed. CVE-2026-67231 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.

How severe is CVE-2026-67231?

CVE-2026-67231 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-67231?

Yes. A fix has been recorded for CVE-2026-67231. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-67231 affect?

CVE-2026-67231 affects RabbitMQ Server prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0 (trust-store plugin enabled). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-67231?

Upgrade to the listed fixed versions or disable the trust-store plugin until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
RabbitMQ Server prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0 (trust-store plugin enabled)
impact

TLS client-auth bypass: attacker with issuer DN+serial can present a forged self-signed cert to authenticate and access/abuse the broker.

action required

Immediate action required

affected versions
rabbitmq rabbitmq-server
  • affected>= 3.13.0 and < 3.13.15
  • affected>= 4.0.0 and < 4.0.20
  • affected>= 4.1.0 and < 4.1.11
  • affected>= 4.2.0 and < 4.2.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free