Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-67237: RabbitMQ is a messaging and streaming broker

42
This month
CRITICAL 9.3UPGRADE

CVE-2026-67237 is a critical-severity flaw (CVSS 9.3) affecting rabbitmq server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 a

Why this priority

  • Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score9.3 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.5% (top 61%)
CISA exploited listNo
WeaknessCWE-79
Published2026-09-25
Last modified2026-10-20
Publisher (CNA): GitHub, Inc. · Vendor: broadcom

Share: LinkedIn · X · Reddit

Last updated 2026-10-20 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

broadcom rabbitmq server UPGRADE
Affected: >= 4.2.0 and < 4.2.8 · >= 4.3.0 and < 4.3.2
Fixed in: 4.2.8, 4.3.2
Safe to downgrade to: a release before 4.2.0
1. Check installed version
apt-cache policy rabbitmq-server || rpm -q rabbitmq-server || rabbitmq-server --version
2. UPGRADE to 4.2.8 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade rabbitmq-server
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade rabbitmq-server
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.2.0 (Debian / Ubuntu)
apt-cache madison rabbitmq-server sudo apt install rabbitmq-server=<VERSION_BEFORE_4.2.0> sudo apt-mark hold rabbitmq-server
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list rabbitmq-server sudo dnf downgrade rabbitmq-server-<VERSION_BEFORE_4.2.0> sudo dnf versionlock add rabbitmq-server
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-67237?

rabbitmq server: upgrade to 4.2.8, 4.3.2. Exact commands for each OS are on this page.

Is CVE-2026-67237 being exploited?

CVE-2026-67237 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-67237 affect?

CVE-2026-67237 affects rabbitmq server. Severity is critical (CVSS 9.3). 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 attacke

How urgent is CVE-2026-67237?

Priority 42/100. Critical severity

Software pages

RabbitMQ vulnerabilities · Bootstrap vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.