CVE-2026-67421

RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling

MEDIUM

6.8

CVSS Score

Published: September 25, 2026 at 04:39 PM UTC

Updated: October 6, 2026 at 07:53 PM UTC

2 products affected across 2 vendorsRabbitmq ServerRabbitmq Server

Using rabbitmq-server by rabbitmq?

Get instant alerts when new vulnerabilities affect rabbitmq-server - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.8

Exploit prediction

EPSS 0.3%

SSVC

PoC

Description

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, RabbitMQ Management rendered an AMQP authorization-error reason containing an attacker-controlled queue name as HTML when the OAuth management UI was enabled. Exploitation requires an attacker with queue configure permission, a management administrator who can see but cannot read that queue, and the administrator clicking Get Message(s). A queue name containing a base element can then retarget the automatic relative refresh because the Content Security Policy omits base-uri and connect-src, and an attacker endpoint that permits the management origin through CORS can receive the victim's Authorization header. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Rabbitmq Server · Broadcom

95%

3.13.0 ≤ v < 3.13.94.0.0 ≤ v < 4.0.244.1.0 ≤ v < 4.1.154.2.0 ≤ v < 4.2.104.3.0 ≤ v < 4.3.5

Affected range stops below 3.13.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.0.24, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.1.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.2.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.3.5, so it looks safe — our inference, not a vendor statement

Rabbitmq Server · Rabbitmq

60%

v < 3.13.19v < 4.0.24v < 4.1.15v < 4.2.10v < 4.3.5

Affected range stops below 3.13.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.0.24, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.1.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.2.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.3.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (3)

x_refsource_CONFIRMExploitVendor Advisory

Source: cverecord

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6256-27fm-4rgr

x_refsource_MISCPatch

Source: cverecord

https://github.com/rabbitmq/rabbitmq-server/commit/ff595eaaa6d4f580f72fa04801ffd35f48c46027

x_refsource_MISCRelease Notes

Source: cverecord

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.8MEDIUM[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: HIGH
User Interaction: REQUIRED
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-862

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card