CVE-2026-77406: RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration

Published Sep 16, 2026
·
Updated

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQos is absent. Values such as -1 therefore wrap to 65535 or 4294967295 instead of being rejected. An application that permits untrusted configuration of these Qos values can unintentionally request extremely large prefetch limits, allowing a broker to deliver enough queued messages to exhaust client memory and disrupt processing. This issue is fixed in version 1.13.0.

Affected Software

1 affected component
amqp091-go<1.13.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade RabbitMQ amqp091-go to a version that resolves this vulnerability.

    Fixed in 1.13.0

Event History

Sep 16, 2026
CVE Published
via MITRE·02:37 PM
Data Sourced
via MITRE·02:37 PM
DescriptionWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications using amqp091-go before version 1.13.0 are exposed if untrusted input can control the prefetchCount or prefetchSize arguments passed to Channel.Qos. The resulting oversized prefetch request can cause the broker to deliver enough queued messages to exhaust the client's memory.

2

What input is needed to trigger the oversized prefetch request?

A negative Qos prefetchCount or prefetchSize value is required. For example, -1 is cast to 65535 for the uint16 prefetch-count field or 4294967295 for the uint32 prefetch-size field instead of being rejected.

3

What can be done before upgrading?

Do not allow untrusted configuration or user input to set Channel.Qos prefetchCount or prefetchSize. Validate these values before calling Channel.Qos and reject negative values.

4

How can I determine whether an application may be affected?

Review calls to Channel.Qos in applications using amqp091-go versions earlier than 1.13.0. Investigate whether either Qos value can originate from external configuration, user-controlled input, or any source that could supply a negative integer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203