Skip to content
Fencer Intel
medium 6.8

CVE-2026-67421 json

RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling

published 2mo ago modified last mo. also BIT-rabbitmq-2026-67421 , EUVD-2026-87242 , GHSA-6256-27fm-4rgr

cvss
6.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami rabbitmq 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
  • pivotal_software rabbitmq 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
  • vmware rabbitmq 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
  • rabbitmq-server Debian 14 4.3.6-1

debian advisories DEBIAN-CVE-2026-67421

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1

red hat advisories RHSA-2026:67552

  • rabbitmq-server Azure Linux 3.0 3.13.7-10

azure linux advisories AZL-105323

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-67421 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-67421 updated cvss 4.4

rabbitmq-server: rabbitmq-server: Information disclosure via HTML injection in management interface

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    affected: no fix available “Fix deferred”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix RHSA-2026:67552

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6256-27fm-4rgr referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 4.5 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N
CNA 4.0 4.5 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=3.13.0, <3.13.19
>=4.0.0, <4.0.24
>=4.1.0, <4.1.15
>=4.2.0, <4.2.10
>=4.3.0, <4.3.5
3.13.19
4.0.24
4.1.15
4.2.10
4.3.5

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of rabbitmq/rabbitmq-server published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.