UBUNTU-CVE-2026-67220 (CVE-2026-67220)
Vulnerability from osv_ubuntu – Published: 2026-09-24 00:00 – Updated: 2026-09-24 00:00 – Source websiteRabbitMQ 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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.5.7-1ubuntu0.16.04.4+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.5.7-1ubuntu0.16.04.4+esm2?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.5.4-1",
"3.5.4-3",
"3.5.4-3.1",
"3.5.7-1",
"3.5.7-1ubuntu0.16.04.1",
"3.5.7-1ubuntu0.16.04.2",
"3.5.7-1ubuntu0.16.04.4",
"3.5.7-1ubuntu0.16.04.4+esm1",
"3.5.7-1ubuntu0.16.04.4+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.6.10-1ubuntu0.5"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.6.10-1ubuntu0.5?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.6.10-1",
"3.6.10-1ubuntu0.1",
"3.6.10-1ubuntu0.3",
"3.6.10-1ubuntu0.4",
"3.6.10-1ubuntu0.5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.8.3-0ubuntu0.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.8.3-0ubuntu0.3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.7.8-4ubuntu2",
"3.7.18-1",
"3.8.2-0ubuntu1",
"3.8.2-0ubuntu1.1",
"3.8.2-0ubuntu1.2",
"3.8.2-0ubuntu1.3",
"3.8.2-0ubuntu1.4",
"3.8.2-0ubuntu1.5",
"3.8.3-0ubuntu0.1",
"3.8.3-0ubuntu0.2",
"3.8.3-0ubuntu0.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.9.27-0ubuntu0.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.9.27-0ubuntu0.2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.8.9-3ubuntu1",
"3.9.8-1",
"3.9.8-2",
"3.9.8-3",
"3.9.8-5",
"3.9.8-6",
"3.9.13-1",
"3.9.13-1ubuntu0.22.04.1",
"3.9.13-1ubuntu0.22.04.2",
"3.9.27-0ubuntu0.1",
"3.9.27-0ubuntu0.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.12.1-1ubuntu1.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.12.1-1ubuntu1.4?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.12.1-1",
"3.12.1-1ubuntu1",
"3.12.1-1ubuntu1.2",
"3.12.1-1ubuntu1.4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "4.0.5-10ubuntu5"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@4.0.5-10ubuntu5?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.0.5-8ubuntu2",
"4.0.5-10ubuntu1",
"4.0.5-10ubuntu2",
"4.0.5-10ubuntu3",
"4.0.5-10ubuntu4",
"4.0.5-10ubuntu5"
]
}
],
"aliases": [],
"details": "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 (-\u003e 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 \u003c100 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.",
"id": "UBUNTU-CVE-2026-67220",
"modified": "2026-09-24T00:00:00Z",
"published": "2026-09-24T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-67220"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-67220"
},
{
"type": "REPORT",
"url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-r3qr-4h63-mvj2"
},
{
"type": "REPORT",
"url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-67220"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.