Categories
CVE-2026-77406

Vulnerability in github.com/rabbitmq/amqp091-go (CVE-2026-77406)

Summary

Vulnerability in github.com/rabbitmq/amqp091-go (CVE-2026-77406). Risk of unauthorized operations or information disclosure. Exploitable via Qos. Mitigation: upgrade to 1.13.0 or later.

Original description

The description as published by the source.

Summary

A logic and resource exhaustion vulnerability exists in the AMQP client's Quality of Service (Qos) configuration method. The Qos function accepts signed integers (int) for the prefetchCount and prefetchSize parameters but casts them directly to unsigned integers (uint16 and uint32, respectively) when formatting the wire-level frame.

If a developer passes a negative integer (such as -1) to these parameters—frequently intended as a sentinel value meaning "no change" or "no limit"—the application performs an implicit signed-to-unsigned conversion. This wraps the values to their absolute maximum limit ($65535$ and $4294967295$). Consequently, a consumer expecting restricted message delivery rates is suddenly flooded with an unlimited volume of messages, potentially exhausting memory resources and crashing the application.


Vulnerability Details

Mechanism

The bug manifests during the structural assignment inside the channel's Qos method:

// channel.go:795-796
PrefetchCount: uint16(prefetchCount),  // -1 wraps to 65535
PrefetchSize:  uint32(prefetchSize),   // -1 wraps to 4294967295

In Go, converting a negative signed integer to an unsigned integer shifts the value via two's complement arithmetic. Because no boundary validation or signedness check occurs prior to the cast:

  • Passing -1 for prefetchCount yields a wire value of 65535.
  • Passing -1 for prefetchSize yields a wire value of 4294967295.

Impact

The AMQ…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77406 has been found in github.com/rabbitmq/amqp091-go.
Attackers can target a specific entry point like Qos over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/rabbitmq/amqp091-go to 1.13.0 or later.
If unsure, ask your IT team or search "github.com/rabbitmq/amqp091-go CVE-2026-77406" on the vendor's site.

CVE-2026-77406 (github.com/rabbitmq/amqp091-go) — CWE-195
Attack surface: Qos / int / prefetchCount / prefetchSize
Patched: 1.13.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-195) exists in github.com/rabbitmq/amqp091-go. Attackers reach the vulnerable code path via Qos.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/rabbitmq/amqp091-go. Attack surface: Qos / int / prefetchCount / prefetchSize.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.13.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/rabbitmq/amqp091-go' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/rabbitmq/amqp091-go' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/rabbitmq/amqp091-go を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/rabbitmq/amqp091-go to 1.13.0

    ステージング環境で 1.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/rabbitmq/amqp091-go
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details