Skip to content
Fencer Vulns
high 7.1

CVE-2026-67410 json

RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint

published 2026-09-25 44 d ago modified 2026-10-09 31 d ago also BIT-rabbitmq-2026-67410 , EUVD-2026-87238 , GHSA-f9f2-q3jf-wfj3

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami rabbitmq 4.2.9, 4.3.3
  • pivotal_software rabbitmq 4.2.9, 4.3.3
  • vmware rabbitmq 4.2.9, 4.3.3
  • rabbitmq-server Debian 14 4.3.6-1

debian advisories DEBIAN-CVE-2026-67410

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1

red hat advisories RHSA-2026:67552

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-67410 updated cvss 7.5

rabbitmq-server: rabbitmq-server: Sensitive credential disclosure via unauthenticated JavaScript endpoint

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix RHSA-2026:67552
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server Red Hat OpenStack Platform 18.0 rabbitmq-server
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
44 d ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 8.2 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
CNA 4.0 8.2 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
NVD 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=4.2.0, <4.2.9
>=4.3.0, <4.3.3
4.2.9
4.3.3

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.