Is CVE-2026-67404 exploited in the wild?

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

How severe is CVE-2026-67404?

Informational severity, published 23 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-67404?

A patch was published on 2026-04-23: RabbitMQ 4.2.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67404 attacked?

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

Am I affected by CVE-2026-67404?

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-67404: RabbitMQ OAuth2 JWKS signature verification bypass

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

RabbitMQ is a messaging broker used for application communication and data streaming. When configured to use OAuth2 authentication without a certificate bundle and in an environment with no OS-level CA certificates (such as minimal containers), RabbitMQ silently disables certificate verification. An attacker positioned to intercept network traffic can forge authentication tokens, gaining unauthorized access to the message broker.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67404 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67404 being exploited in the wild.
How severe is CVE-2026-67404?: Informational severity, published 23 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-67404?: A patch was published on 2026-04-23: RabbitMQ 4.2.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67404 attacked?: It is attacked over the network or from the adjacent network, in a hosted service.
Am I affected by CVE-2026-67404?: 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 ssl_options/1 function falls back to verify_none without warning when no CA bundle is available, allowing an attacker to forge JWKS responses used for JWT signature validation. This requires the OAuth2 plugin to be active, no cacertfile configured, and the OS CA bundle to be empty or unreadable; the attacker must be in a man-in-the-middle position on the network. The result is acceptance of arbitrary JWTs, bypassing authentication controls.

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: GitHub security advisory GHSA-37wx-r6q9-6fhj published
2026-04-23: patched: RabbitMQ 4.2.6 released
2026: patched: Versions 3.13.15, 4.0.20, 4.1.11, 4.3.0 released with fixes

References

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