Is CVE-2026-67220 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67220 being exploited in the wild.

How severe is CVE-2026-67220?

Informational severity, published 23 September 2026.

Which products and versions are affected?

Broadcom RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5.

Is there a fix for CVE-2026-67220?

A patch was published on 2026-04-23: v4.2.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67220 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-67220?

Check whether you run Broadcom RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67220: RabbitMQ JMS topic exchange atom exhaustion denial of service

CVE-2026-67220 · Severity: info · Published 2026-09-23

RabbitMQ is a message broker used to route messages between applications. When the bundled JMS topic exchange plugin processes binding requests with selector arguments, it does not limit the number of atoms created, allowing an authenticated user to exhaust the broker's atom table and crash the entire server. This denial of service affects all connected users across all virtual hosts, even though the attacker may have limited privileges in a single vhost.

Technologies: Broadcom RabbitMQ. Vendors: Broadcom.

Quick answers

Is CVE-2026-67220 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67220 being exploited in the wild.
How severe is CVE-2026-67220?: Informational severity, published 23 September 2026.
Which products and versions are affected?: Broadcom RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5.
Is there a fix for CVE-2026-67220?: A patch was published on 2026-04-23: v4.2.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67220 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67220?: Check whether you run Broadcom RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the JMS topic exchange plugin's add_binding/3 function, which passes unsanitized rjms_erlang_selector arguments through erl_scan:string/1 and erl_parse:parse_term/1. Erlang's erl_scan interns every atom literal it encounters with no length cap or validation, and the created atoms cannot be garbage collected by the surrounding try/catch. An authenticated AMQP user with read permission on an x-jms-topic exchange and write permission on any queue can send crafted binding requests with thousands of unique atom names per request, exhausting the 1M-entry atom table within ~70 bind calls and causing system_limit crash.

Affected products

Broadcom RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5

Timeline

2026-07-09: disclosed
2026-04-23: patched: v4.2.6 released
2026-09-23: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.