Quick answers
- Is CVE-2026-67410 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67410 being exploited in the wild.
- How severe is CVE-2026-67410?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- RabbitMQ 4.2.0 to 4.3.2, 4.2.0 to 4.2.8.
- Is there a fix for CVE-2026-67410?
- A patch was published on 2026-07-09. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67410 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-67410?
- Check whether you run 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 is a credential exposure (CWE-200) where the oauthclientsecret configuration value is included in JavaScript served by the /js/oidc-oauth/bootstrap.js endpoint without authentication requirements. The route is registered as a plain Cowboy handler in rabbitmgmtdispatcher.erl without proper access controls. Any network attacker can retrieve the client secret and use it to complete OAuth2 authorization flows or impersonate the RabbitMQ client to the identity provider.
Affected products
- RabbitMQ RabbitMQ 4.2.0 to 4.3.2, 4.2.0 to 4.2.8
Timeline
- 2026-09-25: disclosed
- 2026-07-09: patched