CVE-2026-67237

Source
https://cve.org/CVERecord?id=CVE-2026-67237
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-67237.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-67237
Aliases
  • GHSA-2rf7-f6r6-8rwh
Downstream
Published
2026-09-25T16:05:16Z
Modified
2026-09-26T03:47:11Z
Severity
  • 7.5 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CVSS Calculator
Summary
RabbitMQ: Reflected XSS via the OAuth bootstrap JS endpoint
Details

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, set_token_auth/2 inserted a bearer token from the Authorization header or access_token cookie into OAuth bootstrap JavaScript without escaping, allowing attacker-controlled token content to execute JavaScript in the management UI origin. The endpoint is exposed before authentication only when management.oauth_enabled is true, and exploitation through the cookie path additionally requires the attacker to plant an access_token cookie on the management host. This issue is fixed in versions 4.2.8 and 4.3.2.

Database specific
{
    "cna_assigner":  "GitHub_M",
    "cwe_ids":  [
        "CWE-79"
    ],
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67237.json"
}
References

Affected packages

Git / github.com/rabbitmq/rabbitmq-server

Affected ranges

Type
GIT
Repo
https://github.com/rabbitmq/rabbitmq-server
Events
Database specific
Show details
{
    "extracted_events":  [
        {
            "introduced":  "4.2.0"
        },
        {
            "fixed":  "4.2.8"
        },
        {
            "introduced":  "4.3.0"
        },
        {
            "fixed":  "4.3.2"
        }
    ],
    "source":  "AFFECTED_FIELD"
}

Affected versions

v4.*
v4.2.0
v4.2.1
v4.2.2
v4.2.3
v4.2.4
v4.2.5
v4.2.6
v4.2.7
v4.3.0
v4.3.1

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-67237.json"