Vulnerability in github.com/rabbitmq/amqp091-go (CVE-2026-107386)
Summary
Vulnerability in github.com/rabbitmq/amqp091-go (CVE-2026-107386). Risk of unauthorized operations or information disclosure. Exploitable via connection.tune. Mitigation: upgrade to 1.14.0 or later.
Original description
The description as published by the source.
Summary
The frame-size mitigation released in amqp091-go v1.13.0 can be bypassed before connection.tune completes. A malicious or compromised AMQP peer can send only a seven-byte body-frame header containing a large attacker-controlled uint32 payload length. The client allocates a slice of that declared length before it verifies that the payload exists or rejects the frame for its invalid protocol state.
The bypass occurs because Connection.maxFrameSize starts at zero. The reader interprets zero as both “negotiated unlimited” and “not negotiated yet,” and skips the pre-allocation size check in either case. Open starts the reader goroutine before negotiation and does not store a limit until after it receives connection.tune.
This remains reachable even if the caller explicitly uses Config{FrameSize: frameMinSize}. A malicious broker can therefore cause excessive memory allocation, potentially terminating the Go client process through memory exhaustion, before authentication and connection setup complete.
Relationship to the existing advisory
GHSA-r9c8-gcjp-xfwh describes attacker-controlled, unbounded allocation by a malicious broker and identifies v1.13.0 as the patched version. Pull request 369 added a frame-size check before parser allocation, but the check is active only when the stored maximum is nonzero.
The v1.13.0…
Source: GitHub Security Advisories (Global) 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-107386 has been found in github.com/rabbitmq/amqp091-go.
Attackers can target a specific entry point like connection.tune 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.14.0 or later.
If unsure, ask your IT team or search "github.com/rabbitmq/amqp091-go CVE-2026-107386" on the vendor's site.
CVE-2026-107386 (github.com/rabbitmq/amqp091-go) — CWE-770
Attack surface: connection.tune / uint32 / Connection.maxFrameSize / Open
Patched: 1.14.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.
A vulnerability (CWE-770) exists in github.com/rabbitmq/amqp091-go. Attackers reach the vulnerable code path via connection.tune.
Check the vendor advisory for the affected versions of github.com/rabbitmq/amqp091-go. Attack surface: connection.tune / uint32 / Connection.maxFrameSize / Open.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.14.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/rabbitmq/amqp091-go to 1.14.0ステージング環境で 1.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。