UBUNTU-CVE-2026-67410 (CVE-2026-67410)
Vulnerability from osv_ubuntu – Published: 2026-09-25 17:17 – Updated: 2026-09-30 21:29 – Source websiteRabbitMQ 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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.5.7-1ubuntu0.16.04.4+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.5.7-1ubuntu0.16.04.4+esm2?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.5.4-1",
"3.5.4-3",
"3.5.4-3.1",
"3.5.7-1",
"3.5.7-1ubuntu0.16.04.1",
"3.5.7-1ubuntu0.16.04.2",
"3.5.7-1ubuntu0.16.04.4",
"3.5.7-1ubuntu0.16.04.4+esm1",
"3.5.7-1ubuntu0.16.04.4+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.6.10-1ubuntu0.5"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.6.10-1ubuntu0.5?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.6.10-1",
"3.6.10-1ubuntu0.1",
"3.6.10-1ubuntu0.3",
"3.6.10-1ubuntu0.4",
"3.6.10-1ubuntu0.5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.8.3-0ubuntu0.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.8.3-0ubuntu0.3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.7.8-4ubuntu2",
"3.7.18-1",
"3.8.2-0ubuntu1",
"3.8.2-0ubuntu1.1",
"3.8.2-0ubuntu1.2",
"3.8.2-0ubuntu1.3",
"3.8.2-0ubuntu1.4",
"3.8.2-0ubuntu1.5",
"3.8.3-0ubuntu0.1",
"3.8.3-0ubuntu0.2",
"3.8.3-0ubuntu0.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.9.27-0ubuntu0.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.9.27-0ubuntu0.2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.8.9-3ubuntu1",
"3.9.8-1",
"3.9.8-2",
"3.9.8-3",
"3.9.8-5",
"3.9.8-6",
"3.9.13-1",
"3.9.13-1ubuntu0.22.04.1",
"3.9.13-1ubuntu0.22.04.2",
"3.9.27-0ubuntu0.1",
"3.9.27-0ubuntu0.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "3.12.1-1ubuntu1.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@3.12.1-1ubuntu1.4?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.12.1-1",
"3.12.1-1ubuntu1",
"3.12.1-1ubuntu1.2",
"3.12.1-1ubuntu1.4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rabbitmq-server",
"binary_version": "4.0.5-10ubuntu5"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "rabbitmq-server",
"purl": "pkg:deb/ubuntu/rabbitmq-server@4.0.5-10ubuntu5?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.0.5-8ubuntu2",
"4.0.5-10ubuntu1",
"4.0.5-10ubuntu2",
"4.0.5-10ubuntu3",
"4.0.5-10ubuntu4",
"4.0.5-10ubuntu5"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-67410",
"modified": "2026-09-30T21:29:20Z",
"published": "2026-09-25T17:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-67410"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-67410"
},
{
"type": "REPORT",
"url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3"
},
{
"type": "REPORT",
"url": "https://github.com/rabbitmq/rabbitmq-server/commit/60a85d3605ebf94fd234497242812547d441d457"
},
{
"type": "REPORT",
"url": "https://github.com/rabbitmq/rabbitmq-server/commit/869f800998334bb363f2ad046f58de9caedc409e"
},
{
"type": "REPORT",
"url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9"
},
{
"type": "REPORT",
"url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"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",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-67410"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.