CVE-2026-79921

amqp091-go has a Potential Memory Exhaustion/Protocol Violation via Broker-Controlled Oversized Payload

Published Aug 26, 2026 CVSS 4.0 · 8.9 High EPSS < 1% KEV · Not listed
Description
amqp091-go is a Go AMQP 0.9.1 client. Before version 1.13.0, a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints. Version 1.13.0 contains a fix. No known workarounds are available.

Analysis

AI-generated

Technical impact

A malicious AMQP broker can send content body frames that exceed the negotiated frame_max limit. The amqp091-go client library will allocate memory to buffer these frames and process them, causing unbounded memory consumption and application‑layer denial of service. This flaw, classified as CWE‑770, allows an attacker to bypass the protocol’s framing constraints and force the client to use resources beyond the intended limits, potentially crashing or degrading the application.

Affected Systems

The affected product is the RabbitMQ Go client library amqp091-go. All deployments using versions prior to 1.13.0 are susceptible. The fix was released in version 1.13.0. Clients that rely on older releases and connect to compromised or malicious brokers are at risk.

Risk and Exploitability

The CVSS score of 8.9 marks the vulnerability as high severity. EPSS is not available, and the flaw is not listed in the CISA KEV catalog. Exploitation requires the attacker to have control over the AMQP broker that can inject oversized frames; once this is achieved, the broker can trigger memory exhaustion on the client side, potentially causing the application to crash or become unresponsive. The attack can be carried out over the network from the broker to the client, making remote attackers who can manipulate broker traffic a direct threat.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the amqp091-go client library to version 1.13.0 or later.
  • Restrict client connections to trusted brokers and, if possible, enforce a strict frame_max limit on the broker side to prevent oversized frames.
  • Apply system or container‑level resource limits to bound memory usage, and configure the client process to restart or alert when consumption exceeds a safe threshold.

Generated by OpenCVE AI on August 26, 2026 at 22:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-6c5v-hqjr-5xxp amqp091-go has a Potential Memory Exhaustion/Protocol Violation via Broker-Controlled Oversized Payload
History
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Rabbitmq
Rabbitmq amqp091-go
Vendors & Products Rabbitmq
Rabbitmq amqp091-go
Type Values Removed Values Added
Description amqp091-go is a Go AMQP 0.9.1 client. Before version 1.13.0, a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints. Version 1.13.0 contains a fix. No known workarounds are available.
Title amqp091-go has a Potential Memory Exhaustion/Protocol Violation via Broker-Controlled Oversized Payload
Weaknesses CWE-770
References
Metrics cvssV4_0

{'score': 8.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 29, 2026, 2:50 AM
Reserved
Aug 25, 2026, 2:59 PM
Status
Deferred
Published
Aug 26, 2026, 9:16 PM
Modified
Sep 9, 2026, 9:09 PM
Severity
Important
Public date
Aug 26, 2026, 8:24 PM