Skip to content
Noroxi
CVE-2019-11291· NVD / CVE Program· CNA pivotal

RabbitMQ XSS attack via federation and shovel endpoints

Pivotal RabbitMQ, 3.7 versions prior to v3.7.20 and 3.8 version prior to v3.8.1, and RabbitMQ for PCF, 1.16.x versions prior to 1.16.7 and 1.17.x versions prior to 1.17.4, contain two endpoints, federation and shovel, which do not properly sanitize user input. A remote authenticated malicious user with administrative access could craft a cross site scripting attack via the vhost or node name fields that could grant access to virtual hosts and policy management information.

MediumCVSS 4.8 · v3.1—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Nov 22, 2019
Updated
Jun 16, 2026
EPSS
0.8% · 55th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

19

Monitor

Low priority for now.

CVSS
19 / 40 · 4.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CNA vs NVD score

NVD
4.8
CNA · pivotal
3.1
1.7 point gap

CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
broadcomrabbitmq server
vmwarerabbitmq
redhatopenstack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • broadcom rabbitmq server3.7.0 and later · before 3.7.20
  • broadcom rabbitmq server3.8.0
  • redhat openstack15
  • vmware rabbitmq1.16.0 and later · before 1.16.7
  • vmware rabbitmq1.17.0 and later · before 1.17.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (pivotal). Independent of NVD's CPE analysis and usually ahead of it.

  • Pivotal RabbitMQ

    • 3.8 and later · before v3.8.1affected
    • 3.7 and later · before v3.7.20affected
  • Pivotal RabbitMQ for Pivotal Platform

    • 1.17 and later · before 1.17.4affected
    • 1.16 and later · before 1.16.7affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12rabbitmq-serverbefore 3.8.3-13.8.3-1
Hexrabbit_commonfrom 3.7.0 · before 3.7.203.7.20
Hexrabbit_commonfrom 3.8.0 · before 3.8.13.8.1
Red Hat:openstack:15::el8rabbitmq-serverbefore 0:3.7.23-2.el8ost0:3.7.23-2.el8ost

Other highest-scoring records for the same primary product.

  • CVE-2026-57216RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks
    40Plan
  • CVE-2026-57211RabbitMQ: UNC SSRF affecting the management UI on Windows
    40Plan
  • CVE-2016-9877An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1
    39Monitor
  • CVE-2026-57219RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations
    35Monitor
  • CVE-2021-22117RabbitMQ installers on Windows prior to version 3.8.16 do not harden plugin directory permissions, potentially allowing attackers with suffi
    31Monitor
  • CVE-2019-11287RabbitMQ Web Management Plugin DoS via heap overflow
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:rabbitmq-server3.8.3-1 · Debian:12Package registry (OSV)
Hex:rabbit_common3.7.20Package registry (OSV)
Hex:rabbit_common3.8.1Package registry (OSV)
red hat:rabbitmq-server0:3.7.23-2.el8ost · Red Hat:openstack:15::el8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

nvd-primary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records