Is CVE-2026-67225 exploited in the wild?

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

How severe is CVE-2026-67225?

Informational severity, published 25 September 2026.

Which products and versions are affected?

VMware RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5.

Is there a fix for CVE-2026-67225?

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

How is CVE-2026-67225 attacked?

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

Am I affected by CVE-2026-67225?

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-67225: RabbitMQ stream protocol frame size validation bypass

CVE-2026-67225 · Severity: info · Published 2026-09-25

RabbitMQ is a message broker that handles critical business communications and data flow. When the stream plugin is enabled, an unauthenticated remote attacker can send specially crafted messages that cause the broker to buffer excessive data, exhausting server memory and disrupting service availability. This denial-of-service attack requires no credentials or user interaction.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67225 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67225 being exploited in the wild.
How severe is CVE-2026-67225?: Informational severity, published 25 September 2026.
Which products and versions are affected?: VMware RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5.
Is there a fix for CVE-2026-67225?: A patch was published on 2026-04-23: Fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67225 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67225?: 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 stream protocol negotiates a maximum frame size (FrameMax) during handshake but fails to validate incoming frame declarations against this limit before buffering, allowing resource exhaustion. The vulnerability exists in RabbitMQ versions 3.13.0–3.13.14, 4.0.0–4.0.19, 4.1.0–4.1.10, and 4.2.0–4.2.5 when the stream plugin is enabled. An unauthenticated remote client can trigger excessive memory allocation and denial of service via network-based frame manipulation.

Affected products

VMware RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5

Timeline

2026-07-09: disclosed: Security advisory GHSA-c8c4-gvv4-8j3q published
2026-04-23: patched: Fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0

References

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