GHSA-5cq3-v9jx-p3x3: RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom

Q: Which deployments are affected?

RabbitMQ versions earlier than 3.13.15, 4.0.20, 4.1.11, and 4.2.6 are affected. The issue involves Khepri-backed deletion checks and direct-reply-to destinations.

Q: What access does an attacker need?

The supplied severity vector indicates that network access is possible and low privileges are required. User interaction is not required, but exploitation has high attack complexity.

Q: What is the security impact?

A successful attack can allow unauthorized injection into reply channels and leave persistent phantom route entries. The severity vector indicates high impact to confidentiality, including subsequent-system confidentiality, with no indicated integrity or availability impact.

Q: What should be done to remediate the issue?

Upgrade RabbitMQ to 3.13.15, 4.0.20, 4.1.11, or 4.2.6, as applicable to the deployed release line.

Published Jul 10, 2026

Updated

RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ allows foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues can be accepted at bind and route time but are missing from Khepri-backed deletion checks, leaving persistent route entries after unbind. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

Affected Software

1 affected component

RabbitMQ RabbitMQ<3.13.15, <4.0.20, <4.1.11, <4.2.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade RabbitMQ to a version that resolves this vulnerability.
Fixed in 3.13.15
Upgrade
Upgrade RabbitMQ to a version that resolves this vulnerability.
Fixed in 4.0.20
Upgrade
Upgrade RabbitMQ to a version that resolves this vulnerability.
Fixed in 4.1.11
Upgrade
Upgrade RabbitMQ to a version that resolves this vulnerability.
Fixed in 4.2.6

Event History

Jul 10, 2026

CVE Published

via OSV·08:23 PM

Data Sourced

via OSV·08:23 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are affected?

RabbitMQ versions earlier than 3.13.15, 4.0.20, 4.1.11, and 4.2.6 are affected. The issue involves Khepri-backed deletion checks and direct-reply-to destinations.

What access does an attacker need?

The supplied severity vector indicates that network access is possible and low privileges are required. User interaction is not required, but exploitation has high attack complexity.

What is the security impact?

A successful attack can allow unauthorized injection into reply channels and leave persistent phantom route entries. The severity vector indicates high impact to confidentiality, including subsequent-system confidentiality, with no indicated integrity or availability impact.

What should be done to remediate the issue?

Upgrade RabbitMQ to 3.13.15, 4.0.20, 4.1.11, or 4.2.6, as applicable to the deployed release line.

GHSA-5cq3-v9jx-p3x3: RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are affected?

What access does an attacker need?

What is the security impact?

What should be done to remediate the issue?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are affected?

What access does an attacker need?

What is the security impact?

What should be done to remediate the issue?