Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-67410)
Description
CVE-2026-67410 is a vulnerability in RabbitMQ server versions prior to 4.3.3 and 4.2.9 where the OAuth2 client secret is exposed via an unauthenticated JavaScript endpoint. When OAuth2 authentication is enabled for the RabbitMQ Management UI, the client secret is included in the JavaScript served by the unauthenticated endpoint /js/oidc-oauth/bootstrap.js. This allows any user who can access the management UI port to retrieve the OAuth2 client secret without authentication.
CVSS v3.1
Score 7.1high
Affected software
pkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra-legacy/xenialpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/bionicpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/focalpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=jammypkg:deb/ubuntu/rabbitmq-server?arch=source&distro=noblepkg:deb/ubuntu/rabbitmq-server?arch=source&distro=stonkingpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ versions from 4.2.0 until 4.3.3 and 4.2.9 have a security flaw where the OAuth2 client secret is exposed through the unauthenticated JavaScript endpoint /js/oidc-oauth/bootstrap.js. This occurs when OAuth2 authentication is enabled for the Management UI and the configured flow uses a client secret. The secret is embedded in the JavaScript served by this endpoint, which is accessible without authentication. This exposure can lead to credential theft, allowing an attacker to complete the OAuth2 authorization code flow using stolen authorization codes and impersonate clients to make unauthorized requests. The issue is fixed in RabbitMQ versions 4.3.3 and 4.2.9.
Potential Impact
The vulnerability allows any unauthenticated user with network access to the RabbitMQ Management UI port to retrieve the OAuth2 client secret. This can lead to unauthorized access by enabling attackers to complete the OAuth2 authorization code flow, potentially impersonating legitimate clients and making unauthorized requests. The confidentiality of the OAuth2 client secret is compromised, which may result in partial loss of confidentiality and integrity of the authentication process.
Mitigation Recommendations
This vulnerability is fixed in RabbitMQ versions 4.3.3 and 4.2.9. Users should upgrade to at least these versions to remediate the issue. No additional mitigation steps are required if these versions are deployed.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-67410
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.10","Ubuntu:26.04:LTS"]
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad3f5a72cdf04f6566627d8
Added to database: 10/17/2026, 22:24:39 UTC
Last enriched: 10/17/2026, 23:54:56 UTC
Last updated: 10/17/2026, 23:54:56 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.