Skip to content
Fencer Vulns
critical 9.1

CVE-2026-77408 json

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

published 2026-09-16 53 d ago modified 2026-10-01 38 d ago also GHSA-j497-x9hr-x34x , GO-2026-6498 , EUVD-2026-80791

cvss
9.1
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/rabbitmq/amqp091-go 1.13.0
  • golang-github-rabbitmq-amqp091-go Debian 14 1.14.0-1

debian advisories DEBIAN-CVE-2026-77408

  • telegraf Azure Linux 3.0 1.31.0-34

azure linux advisories AZL-103275

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-77408 updated cvss 5.3

github.com/rabbitmq/amqp091-go: RabbitMQ amqp091-go: Silent Data Truncation and State Corruption via Shortstr Integer Overflow

  • Red Hat Cryostat 4 cryostat/cryostat-storage-rhel9
    affected: workaround, no fix available
  • Red Hat Multicluster Global Hub multicluster-globalhub/multicluster-globalhub-grafana-rhel9 Red Hat OpenShift Serverless openshift-serverless-1/kn-plugin-event-sender-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/volsync-rhel9, rhacm2/acm-grafana-rhel9, rhacm2/volsync-operator-bundle
    affected: workaround, no fix available, no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 18.0 rhoso-operators/rabbitmq-cluster-rhel9-operator
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Quay 3 quay/clair-rhel8, quay/clair-rhel9
    affected: workaround, no fix available, no fix planned “Out of support scope”
  • Red Hat Custom Metric Autoscaler operator for Red Hat Openshift custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9, custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel9, custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator, custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel9 Red Hat Hardened Images opentelemetry-collector-contrib 0.162.0-0.1.hum1
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
53 d ago

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 9.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:L
CNA 4.0 9.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
go github.com/rabbitmq/amqp091-go
<1.13.0
1.13.0

Affected products

  • rabbitmq amqp091-go

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.