CVE-2026-77408: RabbitMQ amqp091-go: Silent Data Truncation and State Corruption via Shortstr Integer Overflow

Published Sep 16, 2026
·
Updated

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, the writeShortstr function in write.go casts the byte length of AMQP shortstr property values to uint8 without first rejecting values longer than 255 bytes. An application that accepts an oversized CorrelationId, ReplyTo, MessageId, Expiration, UserId, AppId, ContentType, ContentEncoding, or Type value can therefore serialize a wrapped length and only a truncated prefix, while reporting no error. The resulting silent metadata corruption can break request and reply correlation, routing, tracing, and downstream message 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:30 PM
Data Sourced
via MITRE·02:30 PM
DescriptionWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications using RabbitMQ amqp091-go versions before 1.13.0 are affected if they can supply AMQP shortstr property values longer than 255 bytes for fields such as CorrelationId, ReplyTo, MessageId, Expiration, UserId, AppId, ContentType, ContentEncoding, or Type.

2

What input is required to trigger the problem?

An oversized value exceeding 255 bytes must reach one of the affected AMQP message property fields. The client casts the length to uint8, causing the serialized length to wrap and only a truncated prefix to be written without an error.

3

How can this issue be remediated?

Upgrade RabbitMQ amqp091-go to version 1.13.0, which fixes the issue. Until upgraded, applications should ensure affected shortstr property values do not exceed 255 bytes.

4

What operational symptoms could indicate exploitation or exposure?

The serialization reports no error, so failures may appear as unexpected truncation or corruption of message metadata. This can manifest as broken request-reply correlation, routing, tracing, or downstream message processing.

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