CVE-2026-67410: rabbitmq-server · Information Exposure
Affects rabbitmq-serverSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 4.3.3 or 4.2.9 soon.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.3.3, 4.2.9
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade rabbitmq-server and rabbitmq/rabbitmq-server to 4.3.3 or 4.2.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
GitHubrabbitmq/rabbitmq-serverpkg:github/rabbitmq/rabbitmq-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade RabbitMQ server to version 4.2.9 or later if using the 4.2.x branch, or to version 4.3.3 or later if using the 4.3.x branch. These versions contain the official fix that prevents exposure of the OAuth2 client secret via the unauthenticated JavaScript endpoint. No other mitigation is required once the upgrade is applied.
Description
CVE-2026-67410 is a vulnerability in RabbitMQ server versions 4.2.0 through 4.2.8 and 4.3.0 through 4.3.2 where the OAuth2 client secret is exposed via an unauthenticated JavaScript endpoint. This occurs when OAuth2 authentication is enabled for the RabbitMQ Management UI and the configured flow uses a client secret. The secret is included in the JavaScript served by the unauthenticated endpoint /js/oidc-oauth/bootstrap.js, allowing any user who can access the management UI port to retrieve it. The issue is fixed in versions 4.2.9 and 4.3.3.
References
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/commit/60a85d3605ebf94fd234497242812547d441d457 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/commit/869f800998334bb363f2ad046f58de9caedc409e (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3 (opens in a new tab)