CVE-2026-77403: RabbitMQ amqp091-go Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-xwwf-m8fg-p9q2
CWE-770
Published
Advisory Summary

CVE-2026-77403 is a HIGH denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting RabbitMQ amqp091-go libraries in the Go ecosystem. The issue involves denial of service via sub-spec frame size negotiation. Remediation is available by upgrading affected packages to version 1.13.0.

CVE-2026-77403 at a Glance

CVE Identifier CVE-2026-77403
GHSA Identifier GHSA-xwwf-m8fg-p9q2
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product RabbitMQ amqp091-go
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-77403

To remediate this vulnerability, upgrade all affected RabbitMQ amqp091-go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rabbitmq/amqp091-go fixed: 1.13.0
Upgrade github.com/rabbitmq/amqp091-go to 1.13.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rabbitmq/amqp091-go

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-77403, inspect your project dependencies for RabbitMQ amqp091-go:

inspect dependencies for github.com/rabbitmq/amqp091-go

Analyze the terminal output to locate any version of RabbitMQ amqp091-go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.13.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In RabbitMQ amqp091-go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary A Denial of Service (DoS) vulnerability exists in the AMQP client's connection negotiation logic. The AMQP specification explicitly mandates a strict minimum frame size of 4096 bytes to prevent pathological packet fragmentation. While the library defines a `frameMinSize = 4096` constant, the connection negotiation loop fails to enforce this boundary, blindly accepting whatever maximum frame size (`FrameMax`) the server advertises during the handshake. If a client connects to a malicious or compromised AMQP broker that advertises an extremely low `FrameMax` (such as 1 byte), the negotiation succeeds. Consequently, every subsequent message transmission is forced to splinter into thousands or millions of single-byte frames, causing massive CPU overhead, thread contention, and a near-instantaneous application freeze. --- ## Vulnerability Details ### Mechanism During the connection establishment phase, the client and server negotiate connection parameters—including maximum channel count, heartbeat intervals, and maximum frame sizes. The vulnerability is located where the client accepts the server's tuning parameters: ```go // Connection negotiation logic maps server values directly without validation if serverSettings.FrameMax > 0 { // VULNERABILITY: Lacks a floor validation check against frameMinSize (4096) c.config.FrameMax = serverSettings.FrameMax } ``` Because there is no conditional check asserting that `serverSettings.FrameMax >= frameMinSize`, a value below the protocol specification floor is successfully registered. When the application later passes data payloads to the frame writer, the chunking algorithm splits the payload using the negotiated `FrameMax` value as its chunk window divisor. ### Impact When `FrameMax` is set to an absurdly low threshold (e.g., 1 to 10 bytes): * A standard 10 KiB message payload requires tens of thousands of individual write operations and frame headers. * The system's CPU becomes entirely bound by frame serialization, memory allocation for frame structures, and context switching within the network output loops. * This results in an application-layer Denial of Service (DoS) affecting not just the specific AMQP connection, but potentially the entire host system due to CPU resource starvation. --- ## Attack Vector An attacker who compromises an upstream AMQP broker, performs a Man-in-the-Middle (MitM) interception, or tricks an application into connecting to an unauthorized external rogue broker can trigger this vulnerability: 1. **Rogue Handshake:** The client application connects to an AMQP endpoint controlled by the attacker. 2. **Malicious Parameter Tuning:** During the `connection.tune` phase, the rogue server returns a `FrameMax` value of `1`. 3. **Resource Exhaustion Trigger:** The client completes the handshake successfully. As soon as the client attempts to publish a message or process traffic, the internal loop fragments the data into single-byte frames, spiking the host's CPU usage to 100% and disabling the application thread.

CVE-2026-77403 Affected RabbitMQ amqp091-go Versions

1 component(s)
Fixed Versions:
1.13.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rabbitmq/amqp091-go
Go
< 1.13.0
1.13.0

References

Frequently Asked Questions

What is CVE-2026-77403?
CVE-2026-77403 is a security vulnerability in RabbitMQ amqp091-go involving Denial of Service via Sub-Spec Frame Size Negotiation under CWE-770: Allocation of Resources Without Limits or Throttling.
Which RabbitMQ amqp091-go versions are affected?
Affected versions include releases prior to 1.13.0 across affected packages: github.com/rabbitmq/amqp091-go.
What version fixes CVE-2026-77403?
Upgrading to 1.13.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rabbitmq/amqp091-go affected?
Yes, github.com/rabbitmq/amqp091-go is affected in releases prior to 1.13.0. Upgrade your dependency to 1.13.0 or later.
What CWE is associated with CVE-2026-77403?
CVE-2026-77403 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Go dependencies for CVE-2026-77403?
Run the dependency tree command: 'inspect dependencies for github.com/rabbitmq/amqp091-go'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xwwf-m8fg-p9q2",
  "modified" : "2026-09-17T17:03:50Z",
  "published" : "2026-09-17T17:03:50Z",
  "aliases" : [ "CVE-2026-77403" ],
  "summary" : "RabbitMQ amqp091-go: Denial of Service via Sub-Spec Frame Size Negotiation",
  "details" : "## Summary\nA Denial of Service (DoS) vulnerability exists in the AMQP client's connection negotiation logic. The AMQP specification explicitly mandates a strict minimum frame size of 4096 bytes to prevent pathological packet fragmentation. While the library defines a `frameMinSize = 4096` constant, the connection negotiation loop fails to enforce this boundary, blindly accepting whatever maximum frame size (`FrameMax`) the server advertises during the handshake.\n\nIf a client connects to a malicious or compromised AMQP broker that advertises an extremely low `FrameMax` (such as 1 byte), the negotiation succeeds. Consequently, every subsequent message transmission is forced to splinter into thousands or millions of single-byte frames, causing massive CPU overhead, thread contention, and a near-instantaneous application freeze.\n\n---\n\n## Vulnerability Details\n\n### Mechanism\nDuring the connection establishment phase, the client and server negotiate connection parameters—including maximum channel count, heartbeat intervals, and maximum frame sizes. The vulnerability is located where the client accepts the server's tuning parameters:\n\n```go\n// Connection negotiation logic maps server values directly without validation\nif serverSettings.FrameMax > 0 {\n    // VULNERABILITY: Lacks a floor validation check against frameMinSize (4096)\n    c.config.FrameMax = serverSettings.FrameMax \n}\n```\n\nBecause there is no conditional check asserting that `serverSettings.FrameMax >= frameMinSize`, a value below the protocol specification floor is successfully registered. When the application later passes data payloads to the frame writer, the chunking algorithm splits the payload using the negotiated `FrameMax` value as its chunk window divisor.\n\n### Impact\nWhen `FrameMax` is set to an absurdly low threshold (e.g., 1 to 10 bytes):\n* A standard 10 KiB message payload requires tens of thousands of individual write operations and frame headers.\n* The system's CPU becomes entirely bound by frame serialization, memory allocation for frame structures, and context switching within the network output loops.\n* This results in an application-layer Denial of Service (DoS) affecting not just the specific AMQP connection, but potentially the entire host system due to CPU resource starvation.\n\n---\n\n## Attack Vector\nAn attacker who compromises an upstream AMQP broker, performs a Man-in-the-Middle (MitM) interception, or tricks an application into connecting to an unauthorized external rogue broker can trigger this vulnerability:\n\n1. **Rogue Handshake:** The client application connects to an AMQP endpoint controlled by the attacker.\n2. **Malicious Parameter Tuning:** During the `connection.tune` phase, the rogue server returns a `FrameMax` value of `1`.\n3. **Resource Exhaustion Trigger:** The client completes the handshake successfully. As soon as the client attempts to publish a message or process traffic, the internal loop fragments the data into single-byte frames, spiking the host's CPU usage to 100% and disabling the application thread.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rabbitmq/amqp091-go"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.13.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-xwwf-m8fg-p9q2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-77403"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/pull/353"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/commit/2e0a919b89f337dbf58db2bb34ab206dac354a06"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rabbitmq/amqp091-go"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-17T17:03:50Z",
    "nvd_published_at" : "2026-09-16T15:17:46Z"
  }
}