8.2

CVE-2026-67409: broadcom rabbitmq_server Unchecked Return Value

CVSS: 8.2v4.0HighAnalyzed
AliasesUBUNTU-CVE-2026-67409DEBIAN-CVE-2026-67409
Published 25-09-2026Last modified 25-09-2026

Vulnerability summary

CVE-2026-67409 is a high (CVSS 8.2) Unchecked Return Value vulnerability in broadcom rabbitmq_server. EPSS estimates a 0.42% chance of exploitation in the next 30 days, higher than 34.6% of scored vulnerabilities. 1 public exploit is recorded.

Overall risk
43/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.2/10
010
High · v4.0 (CVE.org)
EPSS score
0.42%
0%100%
Low · Change unavailable
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits1github

Advisory lineage

Upstream 0 · Downstream 1 · Related 1

Timeline

  1. 25-09-2026
    PublishedVulnerability first disclosed.
  2. 25-09-2026
    Last modifiedVulnerability information updated.

Description

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18, JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS (CWE-252). the JWKS key fetching mechanism in uaajwt.erl does not validate the HTTP response status code when downloading signing keys from the OAuth2 provider's JWKS endpoint. Non-200 responses (including 4xx and 5xx errors) are processed identically to successful responses. When the JWKS endpoint returns an error response with a valid-JSON body that lacks a keys field, all previously cached signing keys are destroyed, causing a persistent authentication denial of Files: deps/rabbitmqauthbackendoauth2/src/uaajwt.erl, lines 50-63 deps/rabbitmqauthbackendoauth2/src/uaajwks.erl, lines 5-7 deps/rabbitmqauthbackendoauth2/src/rabbitoauth2provider.erl, lines 98-107 Bug 1: HTTP status code ignored (uaajwt.erl:50-63): The Erlang httpc module returns {ok, {{HttpVersion, StatusCode, ReasonPhrase}, Headers, Body}}. The pattern {ok, {, , JwksBody}} matches ANY successful HTTP transaction Persistent authentication DoS: Once keys are destroyed, ALL OAuth2/JWT authentication fails for all users until a new successful JWKS refresh occurs Amplification: A single attacker can deny access to all legitimate OAuth2 users across the entire RabbitMQ. This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18.

CVSS metrics

6 scores · 4 sources · 2 versions

EPSS trend

Probability

0.42%

Chance of exploitation in the next 30 days

Percentile

35%

Versus all other CVEs

30-day change

Change unavailable

Change unavailable

26-09-202618-10-2026
EPSS score
0.42%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

1 found
  • githubUnverified

    Rabbitmq Server

    Maturity: poc

Weaknesses

CWE · root cause

Affected systems

Broadcom1 product
  • rabbitmq_server≥ 3.13.0, < 3.13.18 | ≥ 4.0.0, < 4.0.23 | ≥ 4.1.0, < 4.1.14 | ≥ 4.2.0, < 4.2.9 | ≥ 4.3.0, < 4.3.3
Debian1 product
  • rabbitmq-serverAll versions (No fix recorded) | < 4.3.6-1
Rabbitmq1 product
  • rabbitmq-server≥ 4.3.0, < 4.3.3 | ≥ 4.2.0, < 4.2.9 | ≥ 4.1.0, < 4.1.14 | ≥ 4.0.0, < 4.0.23 | ≥ 3.13.0, < 3.13.18
Ubuntu1 product
  • rabbitmq-serverAll versions (No fix recorded) | < 3.5.7-1ubuntu0.16.04.4+esm3 | < 3.6.10-1ubuntu0.5+esm1 | < 3.8.3-0ubuntu0.3+esm2 | < 3.9.27-0ubuntu0.6 | < 3.12.1-1ubuntu1.7 | < 4.0.5-10ubuntu5.2

4 vendors · 4 products

References

7 links