---
title: "CVE-2026-67409\n    | Ubuntu"
description: Ubuntu is an open source software operating system that runs from the
  desktop, to the cloud, to all your internet connected things.
url: https://ubuntu.com/security/CVE-2026-67409?format=md
keywords: index, follow
---

# CVE-2026-67409

Publication date 29 September 2026

Last updated 30 September 2026

---

Ubuntu priority

**Medium**

[Why this priority?](https://ubuntu.com/security/cves/about#priority )

Toggle side navigation

## 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.

## Status

Show unmaintained releases

| Package | Ubuntu Release | Status |
| --- | --- | --- |
| rabbitmq-server | 26.04 LTS resolute | Needs evaluation |
| 24.04 LTS noble | Needs evaluation |
| 22.04 LTS jammy | Needs evaluation |
| 20.04 LTS focal | Needs evaluation |
| 18.04 LTS bionic | Needs evaluation |
| 16.04 LTS xenial | Needs evaluation |

---

* [How can I get the fixes?](https://ubuntu.com/security/cves/about#security)
* [What do statuses mean?](https://ubuntu.com/security/cves/about#statuses)

## Severity score breakdown

CVSS version:
CVSS v4.0

**Base score**

8.2 · High

* Base metrics

  | Parameter | Value |
  | --- | --- |
  | Attack vector | Network |
  | Attack complexity | Low |
  | Attack requirements | Present |
  | Privileges required | None |
  | User interaction | None |
  | Vulnerable system - Confidentiality impact | None |
  | Vulnerable system - Integrity impact | None |
  | Vulnerable system - Availability impact | High |
  | Subsequent system - Confidentiality impact | None |
  | Subsequent system - Integrity impact | None |
  | Subsequent system - Availability impact | None |
* Scores

  | Parameter | Value |
  | --- | --- |
  | Base score | 8.2 · High |
  | Base + Threat score | - |
  | Base + Environmental score | - |
  | Base + Threat + Environmental score | - |

**Vector:** CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

## References

* [MITRE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-67409)
* [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-67409)
* [Launchpad](https://launchpad.net/bugs/cve/CVE-2026-67409)
* [Debian](https://security-tracker.debian.org/tracker/CVE-2026-67409)

### Other references

* <https://www.cve.org/CVERecord?id=CVE-2026-67409>
* <https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-qw3h-qqm9-jrw8>
* <https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9>
* <https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3>
