---
id: CVE-2026-67237
title: RabbitMQ is a messaging and streaming broker
summary: >-
  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 atta…
severity: high
cvss: 7.5
cvssVector: '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'
cwe:
  - CWE-79
vendor: rabbitmq
product: rabbitmq-server
affected:
  - 'rabbitmq-server >= 4.2.0, < 4.2.8'
  - 'rabbitmq-server >= 4.3.0, < 4.3.2'
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T18:17:29.833'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-67237'
references:
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed917d98828af23
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed082fe6b83fb
    label: security-advisories@github.com
  - url: 'https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8'
    label: security-advisories@github.com
  - url: 'https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2'
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2rf7-f6r6-8rwh
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-09-25T17:53:50.928309Z'
cvssSource: cna
ingestedAt: '2026-09-25T17:13:14.029Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.