cve.bz

CVE-2026-67235 broadcom rabbitmq server

7.1 highEPSS 0.3%

High (7.1) in broadcom rabbitmq server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.1 high
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

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67235 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67235?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67235?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67235 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
broadcom:rabbitmq_serverfrom 3.13.0 before 3.13.15
broadcom:rabbitmq_serverfrom 4.0.0 before 4.0.20
broadcom:rabbitmq_serverfrom 4.1.0 before 4.1.11
broadcom:rabbitmq_serverfrom 4.2.0 before 4.2.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13rabbitmq-serverno fix listedDEBIAN-CVE-2026-67235
Debian14rabbitmq-server4.3.0-2DEBIAN-CVE-2026-67235
Ubuntu22.04:LTSrabbitmq-server3.9.27-0ubuntu0.6UBUNTU-CVE-2026-67235 USN-8933-1
Ubuntu24.04:LTSrabbitmq-server3.12.1-1ubuntu1.7UBUNTU-CVE-2026-67235 USN-8933-1
Ubuntu26.04:LTSrabbitmq-server4.0.5-10ubuntu5.2UBUNTU-CVE-2026-67235 USN-8933-1
UbuntuPro:16.04:LTSrabbitmq-server3.5.7-1ubuntu0.16.04.4+esm3UBUNTU-CVE-2026-67235 USN-8933-1
UbuntuPro:18.04:LTSrabbitmq-server3.6.10-1ubuntu0.5+esm1UBUNTU-CVE-2026-67235 USN-8933-1
UbuntuPro:20.04:LTSrabbitmq-server3.8.3-0ubuntu0.3+esm2UBUNTU-CVE-2026-67235 USN-8933-1
Red Hathummingbird:1rabbitmq-server4.30:4.3.6-1.hum1RHSA-2026:67552
Azure Linux3rabbitmq-server3.13.7-10AZL-105798

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat rates this flaw MODERATE in products that ship affected RabbitMQ builds using CVSS v3.1; RabbitMQ’s higher severity reflects CVSS v4 scoring of the same attack conditions. An authenticated AMQP 0-9-1 publisher can bypass message body-size validation by declaring an oversized body and streaming fragments, accumulating memory until publishing is impaired cluster-wide or the broker node runs out of memory.

Red Hat's mitigation

Restrict publish access to trusted clients; broker memory alarms offer only partial protection until an updated build is deployed.

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.6-1.hum1Fixed 2026-09-15RHSA-2026:67552
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverNot affected
Red Hat OpenStack Platform 16.2rabbitmq-serverNot affected
Red Hat OpenStack Platform 17.1rabbitmq-serverNot affected
Red Hat OpenStack Platform 18.0rabbitmq-serverFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67235.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON