cve.bz

CVE-2026-67410 broadcom rabbitmq server

8.2 highExploit referenceEPSS 0.4%Fix available

High (8.2) in broadcom rabbitmq server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.3.3 and 4.2.9, OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint (CWE-200). when OAuth2 authentication is enabled for the RabbitMQ Management UI and the configured flow, IDP use a client secret, the oauthclientsecret configuration value is included in the JavaScript served by the unauthenticated endpoint /js/oidc-oauth/bootstrap.js. Any user who can reach the management UI port can retrieve the OAuth2 client secret without Files: deps/rabbitmqmanagement/src/rabbitmgmtwmauth.erl, line 186 deps/rabbitmqmanagement/src/rabbitmgmtoauthbootstrap.erl, lines 35-50 deps/rabbitmqmanagement/src/rabbitmgmtdispatcher.erl, lines 45-49 (route registration) Code Path: 1. The route /js/oidc-oauth/bootstrap.js is registered as a plain Cowboy handler (rabbitmgmtdispatcher.erl:46): Credential exposure for the affected configuration: OAuth2 client secret is accessible without any authentication Token theft: Attacker can complete the authorization code flow using stolen authorization codes Client impersonation: Attacker can make requests. Any RabbitMQ deployment with: This issue is fixed in versions 4.3.3 and 4.2.9.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67410 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67410?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67410?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67410 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
broadcom:rabbitmq_serverfrom 4.2.0 before 4.2.9
broadcom:rabbitmq_serverfrom 4.3.0 before 4.3.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14rabbitmq-server4.3.6-1DEBIAN-CVE-2026-67410
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 morerabbitmq-serverno fix listedUBUNTU-CVE-2026-67410
Red Hathummingbird:1rabbitmq-server4.30:4.3.6-1.hum1RHSA-2026:67552
Azure Linux3rabbitmq-serverno fix listedAZL-105308

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in rabbitmq-server within the RabbitMQ Management UI OAuth2 implementation. When OAuth2 authentication is enabled and configured with a client secret, the server exposes the client secret in cleartext via the unauthenticated /js/oidc-oauth/bootstrap.js JavaScript endpoint. A remote, unauthenticated attacker who can reach the management interface can retrieve this secret to impersonate the client application, forge authentication requests, or complete unauthorized OAuth2 authorization flows, resulting in a loss of confidentiality.

Red Hat's mitigation

Disable OAuth2 authentication for the RabbitMQ Management UI and revert to internal username/password or mTLS authentication. Alternatively, restrict network access to the management UI port (default 15672) or configure a reverse proxy to block unauthenticated requests to /js/oidc-oauth/bootstrap.js.

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.6-1.hum1Fixed 2026-09-15RHSA-2026:67552
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverNot affected
Red Hat OpenStack Platform 16.2rabbitmq-serverNot affected
Red Hat OpenStack Platform 17.1rabbitmq-serverNot affected
Red Hat OpenStack Platform 18.0rabbitmq-serverNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67410.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON