{"items":[{"id":"NVI-00014146","kind":"vulnerability","title":"RabbitMQ amqp091-go: Denial of Service via Sub-Spec Frame Size Negotiation","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-xwwf-m8fg-p9q2","CVE-2026-77403"],"plain_summary":"GitHub lists this reviewed advisory for github.com/rabbitmq/amqp091-go. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-501c55f8acc703715086779c73154e91"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-501c55f8acc703715086779c73154e91","url":"https://github.com/advisories/GHSA-xwwf-m8fg-p9q2","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-xwwf-m8fg-p9q2","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T19:09:30.244Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-501c55f8acc703715086779c73154e91"],"technology":"github.com/rabbitmq/amqp091-go","known_exclusions":[],"conditions_summary":"## 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 valu","public_affected_ranges":["< 1.13.0"]}],"null_published_at":"2026-11-02T10:00:37.213Z","source_updated_at":"2026-09-17T17:03:52.000Z","source_disclosed_at":"2026-09-17T17:03:50.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T19:09:30.244Z"}],"next_cursor":null,"snapshot_revision":"42594"}