Is CVE-2026-67405 exploited in the wild?

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

How severe is CVE-2026-67405?

Informational severity, published 23 September 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-67405?

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

How is CVE-2026-67405 attacked?

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

Am I affected by CVE-2026-67405?

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-67405: RabbitMQ missing Origin header validation in WebSocket upgrade

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

RabbitMQ is a messaging broker used to handle critical business communications. The Web-MQTT and Web-STOMP plugins failed to validate the Origin header during WebSocket upgrades, allowing attackers to perform cross-site request forgery (CSRF) attacks. When client certificate authentication is enabled, JavaScript code injected by an attacker could trigger automatic certificate presentation, enabling account takeover or unauthorized message access.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67405 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67405 being exploited in the wild.
How severe is CVE-2026-67405?: Informational severity, published 23 September 2026.
Which products and versions are affected?: VMware RabbitMQ 3.13.0 through 3.13.14, 4.0.0 through 4.0.19, 4.1.0 through 4.1.10, 4.2.0 through 4.2.5.
Is there a fix for CVE-2026-67405?: A patch was published on 2026-04-23: Fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67405 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67405?: 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 Web-MQTT and Web-STOMP handlers did not validate the WebSocket Origin header, enabling CSRF attacks where attacker-controlled JavaScript in the victim's browser initiates WebSocket connections. When ssl_cert_login=true or use_http_auth=true (Web-STOMP only) is configured, the browser automatically presents client certificates, allowing an attacker to authenticate as the victim. The vulnerability requires non-default configuration and is harmless under default in-band CONNECT credential configuration. Origin header validation is now configurable via web_mqtt.allow_origins and web_stomp.allow_origins.

Affected products

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

Timeline

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

References

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