Allocation of Resources Without Limits or Throttling Affecting golang-github-rabbitmq-amqp091-go package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.49% (41st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-GOLANGGITHUBRABBITMQAMQP091GO-20746544
  • published10 Oct 2026
  • disclosed8 Oct 2026

Introduced: 8 Oct 2026

NewCVE-2026-107386  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest golang-github-rabbitmq-amqp091-go.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-github-rabbitmq-amqp091-go package and not the golang-github-rabbitmq-amqp091-go package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

amqp091-go is a Go AMQP 0.9.1 client. From 1.13.0 until 1.14.0, the frame-size mitigation from the prior allocation advisory can be bypassed before connection.tune completes because Connection.maxFrameSize uses zero for both the not-yet-negotiated and negotiated-unlimited states. A malicious or compromised AMQP peer can send a short body-frame header with a large declared payload length, causing ReadFrame and the body-frame parser to allocate attacker-selected memory before the payload is received or the frame's protocol state is rejected. The condition is reachable through public Open even when Config.FrameSize is set to the protocol minimum and can cause severe memory pressure, out-of-memory termination, or loss of the client process before authentication completes. This issue is fixed in version 1.14.0.

CVSS Base Scores

version 3.1