Skip to content
Fencer Vulns
medium 6.5

CVE-2026-67220 json

RabbitMQ: JMS topic exchange erl_scan atom exhaustion

published 2026-09-23 46 d ago modified 2026-10-20 20 d ago also BIT-rabbitmq-2026-67220 , EUVD-2026-85630 , GHSA-r3qr-4h63-mvj2

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, When a binding is created on an x-jms-topic exchange, add_binding/3 reads the rjms_erlang_selector argument and passes it through erl_scan:string/1 then erl_parse:parse_term/1. erl_scan:string/1 interns every atom literal it tokenizes. validate_binding/2 is a no-op (-> ok.), there is no length cap, and the surrounding try/catch cannot reclaim atoms. The Java JMS client compiles selectors client-side, but the server does not enforce this , a raw AMQP client can send arbitrary selector strings. An authenticated low-privilege AMQP user confined to one vhost can crash the entire broker node (cross-tenant DoS) in <100 bind calls. Preconditions include rabbitmq_jms_topic_exchange plugin enabled (bundled; required for any JMS deployment) Authenticated AMQP user with read on an x-jms-topic exchange + write on a queue (or configure to declare both). This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0.

Patch / fix

  • bitnami rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
  • vmware rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
  • pivotal_software rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
  • rabbitmq-server Debian 14 4.3.0-2

debian advisories DEBIAN-CVE-2026-67220

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1

red hat advisories RHSA-2026:67552

  • rabbitmq-server Azure Linux 3.0 3.13.7-10

azure linux advisories AZL-109725

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-67220 updated cvss 6.5

rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: workaround, no fix planned “Disable the JMS topic exchange plugin if unused and restrict binding permissions to trusted users.”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix “Disable the JMS topic exchange plugin if unused and restrict binding permissions to trusted users.” RHSA-2026:67552
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server
    not affected: vulnerable code not present
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
45 d ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 6.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA 4.0 6.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=3.13.0, <3.13.15
>=4.0.0, <4.0.20
>=4.1.0, <4.1.11
>=4.2.0, <4.2.6
3.13.15
4.0.20
4.1.11
4.2.6

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.