RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-67410
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:15 UTC · Revision 1
Source evidence
RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint
core-osv · Original sourcePublished 25 Sept 2026, 16:32 UTC
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.
osv:CVE-2026-67410
Complete source record
{
"id": "ac7e14532ea62b4a038d9217f41f564ea8f64f903c5e45251fd650971690edab",
"url": "https://osv.dev/vulnerability/CVE-2026-67410",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint",
"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.",
"evidence": "osv:CVE-2026-67410",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-67410",
"aliases": [
"BIT-rabbitmq-2026-67410",
"CVE-2026-67410",
"GHSA-f9f2-q3jf-wfj3"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/rabbitmq/rabbitmq-server",
"type": "GIT",
"events": [
{
"introduced": "95c501fbad76c66156346cf364d158d6e30aa4d9"
},
{
"fixed": "47d6d6457c7d1a440daed643cb7d76bba313e79c"
},
{
"introduced": "1929eeadf9b2bac12c5434fb56884ef27370580e"
},
{
"fixed": "1d284b2d2a1e2f845ad22b0d5ee38ec372d50802"
},
{
"fixed": "60a85d3605ebf94fd234497242812547d441d457"
},
{
"fixed": "869f800998334bb363f2ad046f58de9caedc409e"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.9"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.3.0"
},
{
"fixed": "4.3.3"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "60a85d3605ebf94fd234497242812547d441d457"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "869f800998334bb363f2ad046f58de9caedc409e"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "47d6d6457c7d1a440daed643cb7d76bba313e79c"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.2.9"
},
{
"range": [
{
"fixed": "1d284b2d2a1e2f845ad22b0d5ee38ec372d50802"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.3.3"
}
]
}
}
],
"versions": [
"v4.2.8",
"v4.3.2",
"v4.2.7",
"v4.3.1",
"v4.2.6",
"v4.3.0",
"v4.2.5",
"v4.2.4",
"v4.2.3",
"v4.2.2",
"v4.2.1",
"v4.2.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-67410.json"
}
}
],
"modified": "2026-10-28T02:30:22.811418161Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9",
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67410.json",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3",
"https://nvd.nist.gov/vuln/detail/CVE-2026-67410",
"https://github.com/rabbitmq/rabbitmq-server/commit/60a85d3605ebf94fd234497242812547d441d457",
"https://github.com/rabbitmq/rabbitmq-server/commit/869f800998334bb363f2ad046f58de9caedc409e"
],
"provider_metadata": {
"cwe_ids": [
"CWE-200"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67410.json"
}
},
"related_cves": [
{
"value": "CVE-2026-67410",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489032,
"published_at": "2026-09-25T16:32:51.225+00:00"
}