Skip to content
Fencer Vulns
medium 6.5

CVE-2026-67235 json

RabbitMQ: AMQP 0-9-1 body assembly never validates accumulated size

published 2026-09-23 46 d ago modified 2026-10-20 19 d ago also BIT-rabbitmq-2026-67235 , EUVD-2026-85652 , GHSA-q8g2-pc7m-m3jw

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 23%
public exploits
0
none known

Summary

RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQP 0-9-1 is the most widely used protocol, and any publisher can trigger this condition. Preconditions include Any authenticated AMQP 0-9-1 client with publish permission can exploit this.. This issue is fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15.

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-67235

  • rabbitmq-server Ubuntu 22.04 LTS 3.9.27-0ubuntu0.6
  • rabbitmq-server Ubuntu 24.04 LTS 3.12.1-1ubuntu1.7
  • rabbitmq-server Ubuntu 26.04 LTS 4.0.5-10ubuntu5.2
  • rabbitmq-server Ubuntu Pro 16.04 LTS 3.5.7-1ubuntu0.16.04.4+esm3
  • rabbitmq-server Ubuntu Pro 18.04 LTS 3.6.10-1ubuntu0.5+esm1
  • rabbitmq-server Ubuntu Pro 20.04 LTS 3.8.3-0ubuntu0.3+esm2

ubuntu advisories UBUNTU-CVE-2026-67235

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • 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-105798

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-67235 updated cvss 6.5

rabbitmq-server: RabbitMQ: Denial of Service via AMQP 0-9-1 body size validation bypass

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: workaround, no fix planned “Restrict publish access to trusted clients; broker memory alarms offer only partial protection until an updated build is deployed.”
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    affected: workaround, no fix available “Restrict publish access to trusted clients; broker memory alarms offer only partial protection until an updated build is deployed.”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix “Restrict publish access to trusted clients; broker memory alarms offer only partial protection until an updated build is deployed.” 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 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.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 7.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA 4.0 7.1 CVSS:4.0/AV:N/AC:L/AT:N/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-770 Allocation of Resources Without Limits or Throttling

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.