Is CVE-2026-66071 exploited in the wild?

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

How severe is CVE-2026-66071?

Informational severity, published 25 September 2026.

Which products and versions are affected?

VMware RabbitMQ 3.13.0 until 3.13.15, 4.0.x until 4.0.22, 4.1.x until 4.1.11, 4.2.x until 4.2.6, 4.3.0 until 4.3.1.

Is there a fix for CVE-2026-66071?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-66071 attacked?

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

Am I affected by CVE-2026-66071?

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-66071: RabbitMQ atom exhaustion in OAuth2 JWT scope parsing

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

RabbitMQ is a message broker used for event streaming and application communication. When OAuth2 authentication is configured with an identity provider that allows user-influenced scope values in signed tokens, an attacker can exhaust Erlang atoms—limited system resources—by submitting logins with novel scope values, potentially causing a denial of service. The vulnerability requires the IdP to permit attacker-influenced scopes in signed tokens.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-66071 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-66071 being exploited in the wild.
How severe is CVE-2026-66071?: Informational severity, published 25 September 2026.
Which products and versions are affected?: VMware RabbitMQ 3.13.0 until 3.13.15, 4.0.x until 4.0.22, 4.1.x until 4.1.11, 4.2.x until 4.2.6, 4.3.0 until 4.3.1.
Is there a fix for CVE-2026-66071?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-66071 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-66071?: 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 OAuth2 authentication backend parses JWT scope claims of the form "tag:value" and converts them to Erlang atoms using rabbitdatacoercion:toatom(), without limiting the number of scopes allowed. Although the JWT signature is verified, if the IdP configuration permits user-influenced scope values in signed tokens, an attacker can trigger creation of arbitrary atoms by logging in repeatedly with novel tag values, exhausting the fixed pool of Erlang atoms and causing a denial of service. The fix limits the number of scopes to 2048 per token.

Affected products

VMware RabbitMQ 3.13.0 until 3.13.15, 4.0.x until 4.0.22, 4.1.x until 4.1.11, 4.2.x until 4.2.6, 4.3.0 until 4.3.1

Timeline

2026-09-25: disclosed

References

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