# CVE-2026-107386: amqp091-go: Pre-negotiation frame limit is not enforced to 4KB > A malicious AMQP peer can cause memory exhaustion and crash the client process by bypassing frame size limits before connection negotiation completes. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Oct 2026 - **Updated:** 9 Oct 2026 - **Also known as:** CLEANSTART-2026-BX72159, CLEANSTART-2026-VR61817, CLEANSTART-2026-ZB44736, DEBIAN-CVE-2026-107386, ECHO-a87c-d3c1-0535, GHSA-w6r9-248c-frg8, GO-2026-6700, MINI-3cq2-56pp-8c53, MINI-3g3g-vhw3-r25f, MINI-3xm3-69f7-fch3, MINI-4p54-976j-x65x, MINI-53vv-37h9-v6mj, MINI-7fcr-jrxc-c38w, MINI-84p8-w4m2-9w96, MINI-87v4-rqqr-mcr7, MINI-8c39-24p8-956r, MINI-9273-2g7v-62vp, MINI-fwwp-2gwj-5cww, MINI-g84c-7q92-h329, MINI-hw6m-55rr-xv3q, MINI-j9h6-9f2m-2v2m, MINI-jg59-2p92-x48q, MINI-mfq8-327h-rrwg, MINI-mq7g-g2qm-h8w3, MINI-p5px-gmm5-4prm, MINI-p72f-j42h-fw9q, MINI-q4r6-w7q7-ffg2, MINI-q5c6-cvj5-6xxv, MINI-v323-hrw7-cjh3, MINI-w289-c24f-6593, MINI-x6gq-7522-h88m, UBUNTU-CVE-2026-107386 ## What is CVE-2026-107386? CVE-2026-107386 is a medium-severity denial of service vulnerability in rabbitmq amqp091-go, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2026-107386? 3 open source packages ship an affected version, including github.com/rabbitmq/amqp091-go. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/rabbitmq/amqp091-go` | Go | All versions | 1.14.0 | | `github.com/rabbitmq/amqp091-go` | Go | All versions | 1.14.0 | | `github.com/rabbitmq/amqp091-go` | Go | All versions | 1.14.0 | ## How do I fix CVE-2026-107386? Upgrade github.com/rabbitmq/amqp091-go to 1.14.0 or later. ## Is CVE-2026-107386 being exploited? There is no known exploitation of CVE-2026-107386 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107386 and fix it if it is affected. What it is: CVE-2026-107386 is a medium-severity denial of service vulnerability in rabbitmq amqp091-go, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-107386 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/rabbitmq/amqp091-go (Go): affected all versions; fixed in 1.14.0 - github.com/rabbitmq/amqp091-go (Go): affected all versions; fixed in 1.14.0 - github.com/rabbitmq/amqp091-go (Go): affected all versions; fixed in 1.14.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-107386/ (Markdown: https://insights.sbomify.com/CVE-2026-107386/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107386 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107386 - OSV: https://osv.dev/vulnerability/CVE-2026-107386 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107386/ Summaries are generated and may contain mistakes; the official description above is the record.