Is CVE-2026-67235 exploited in the wild?

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

How severe is CVE-2026-67235?

Informational severity, published 23 September 2026.

Which products and versions are affected?

VMware RabbitMQ before 3.13.15, 4.0.x before 4.0.20, 4.1.x before 4.1.11, 4.2.x before 4.2.6, 4.3.x before 4.3.0.

Is there a fix for CVE-2026-67235?

A patch was published on 2026-04-23: Fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67235 attacked?

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

Am I affected by CVE-2026-67235?

Check whether you run VMware 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-67235: RabbitMQ unvalidated content-header BodySize memory exhaustion

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

RabbitMQ is a message broker that handles business-critical communication between applications. An authenticated attacker with publishing permissions can declare an extremely large message body size and then stream fragments slowly, causing the broker to accumulate unbounded memory without triggering protective limits. This leads to memory exhaustion on the broker, degrading all publishers cluster-wide or causing the server to crash.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67235 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67235 being exploited in the wild.
How severe is CVE-2026-67235?: Informational severity, published 23 September 2026.
Which products and versions are affected?: VMware RabbitMQ before 3.13.15, 4.0.x before 4.0.20, 4.1.x before 4.1.11, 4.2.x before 4.2.6, 4.3.x before 4.3.0.
Is there a fix for CVE-2026-67235?: A patch was published on 2026-04-23: Fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67235 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67235?: Check whether you run VMware 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 AMQP 0-9-1 protocol handling where the content-header BodySize field (uint64) is not validated against max_message_size when initially declared, but only checked when message assembly completes. An attacker declares body_size = 2^63-1 and streams fragments at will, preventing the size check from firing and causing unbounded memory accumulation in the reader process. This affects any authenticated AMQP 0-9-1 client with publish permissions; the memory alarm provides only reactive mitigation.

Affected products

VMware RabbitMQ before 3.13.15, 4.0.x before 4.0.20, 4.1.x before 4.1.11, 4.2.x before 4.2.6, 4.3.x before 4.3.0

Timeline

2026-09-23: disclosed
2026-04-23: patched: Fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15

References

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