Answer in brief
CVE-2026-77408 records a Critical severity (CVSS 0.0) vulnerability in RabbitMQ amqp091-go: Silent Data Truncation and State Corruption via Shortstr Integer Overflow. The current sources do not mark it as known exploited. The current feed maps rabbitmq/amqp091-go (generic), github.com/rabbitmq/amqp091-go (go), github.com/rabbitmq/amqp091-go (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps rabbitmq/amqp091-go (generic), github.com/rabbitmq/amqp091-go (go), github.com/rabbitmq/amqp091-go (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| rabbitmq/amqp091-gogeneric | <1.13.0 | 1.13.0 |
| github.com/rabbitmq/amqp091-gogo | <1.13.0 | 1.13.0 |
| github.com/rabbitmq/amqp091-gogo | >=0 <1.13.0 | 1.13.0 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.