Remote Message Delivery in RabbitMQ After OAuth Token Expiry

Publication date: 2026-07-10

Last updated on: 2026-07-10

Assigner: GitHub, Inc.

Description

RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, RabbitMQ AMQP 0-9-1 allows an existing consumer to keep receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes because existing consumers are not canceled or reauthorized at delivery time after the channel user state changes. This issue is fixed in version 4.2.6.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-10

Last Modified

2026-07-10

Generated

2026-07-11

AI Q&A

2026-07-11

EPSS Evaluated

N/A

NVD

CVE-2026-57218

Affected Vendors & Products

Vendor	Product	Version / Range
rabbitmq	rabbitmq	4.2.6

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

Executive Summary

This vulnerability exists in RabbitMQ versions prior to 4.2.6, specifically in the AMQP 0-9-1 protocol implementation. It allows an existing consumer to continue receiving messages even after the OAuth token has expired or after a connection secret has been refreshed to reduced scopes. This happens because the existing consumers are not canceled or reauthorized at the time messages are delivered, despite changes in the channel user state.

Impact Analysis

The impact of this vulnerability is that unauthorized message consumption can continue beyond the intended authorization period. This means that a consumer could keep receiving messages even after their access token has expired or their permissions have been reduced, potentially leading to unauthorized access to sensitive or restricted information.

Mitigation Strategies

To mitigate this vulnerability, upgrade RabbitMQ to version 4.2.6 or later, where the issue is fixed.

Hi! I’m here to help you understand CVE-2026-57218. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70