All vulnerabilities

Servers and applications

CVE-2026-67410

OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint (CWE-200)

Severity
High 8.2
Published
23 Jul 2026
Last changed
17 Nov 2026
Added to UpHeron
1 Nov 2026
Fixed in
4.1.14, 4.2.9, 4.3.3
Exploit chance
0.4% in the next 30 daysHigher than 35% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Information exposure (CWE-200)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read data
CVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-f9f2-q3jf-wfj3
Sources
NVD, Project advisories (GitHub)

Description

When OAuth2 authentication is enabled for the RabbitMQ Management UI and the configured flow, IDP use a client secret, the oauth_client_secret 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 authentication.

  • deps/rabbitmq_management/src/rabbit_mgmt_wm_auth.erl, line 186
  • deps/rabbitmq_management/src/rabbit_mgmt_oauth_bootstrap.erl, lines 35-50
  • deps/rabbitmq_management/src/rabbit_mgmt_dispatcher.erl, lines 45-49 (route registration)
  • Administrator configures management.oauth_client_secret = my-confidential-secret in RabbitMQ config
  • Any unauthenticated user sends: GET /js/oidc-oauth/bootstrap.js
  • Response contains JavaScript: set_oauth_settings({"oauth_enabled":true,...,"oauth_client_secret":"my-confidential-secret",...});
  • Attacker extracts oauth_client_secret from the response
From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Workarounds

One of:

  • Avoid using the OAuth 2 flow that needs a client secret
  • Disable rabbitmq_management and use the Prometheus plugin for monitoring
  • Switch from rabbitmq_auth_backend_oauth2 to any other authN/authZ backend

One of:

  • Switch to different setup or IDP, avoiding client secret flow use entirely
  • Disable the rabbitmq_auth_backend_oauth2 plugin and use a different

One of the following:

  • Switch to an OAuth 2 flow that does not require a client secret
  • Disable rabbitmq_auth_backend_oauth2 and use one of the other supported authN, authZ options
Workarounds as given by rabbitmq/rabbitmq-server's security advisory.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 4.1.0 before 4.1.14
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-67410
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67410
  • GitHub Advisory Database https://github.com/advisories/GHSA-f9f2-q3jf-wfj3
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3