{"id":"CVE-2026-77410","aliases":["AZL-103185","AZL-103299","DEBIAN-CVE-2026-77410","EUVD-2026-80810","GHSA-r9c8-gcjp-xfwh","GO-2026-6500","RHSA-2026:68290","ROOT-APP-GOBINARY-CVE-2026-77410","UBUNTU-CVE-2026-77410"],"status":"published","title":"RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","severity":{"version":"4.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","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00524,"percentile":0.44926,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-789"],"published":"2026-09-16T14:39:08Z","modified":"2026-11-02T14:15:30Z","fixes":[{"ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","fixed_in":["1.13.0"],"sources":["ghsa","osv"]},{"ecosystem":"Azure Linux:3","package":"telegraf","fixed_in":["1.31.0-34"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"golang-github-rabbitmq-amqp091-go","fixed_in":["1.14.0-1"],"sources":["osv"]},{"ecosystem":"Root:Go","package":"github.com/rabbitmq/amqp091-go","fixed_in":["v1.10.0-aikido.3","v1.10.0-aikido.4","v1.10.0-aikido.5","v1.10.0-aikido.6","v1.10.0-aikido.7","v1.12.0-aikido.2","v1.12.0-aikido.3","v1.12.0-aikido.4","v1.12.0-aikido.5","v1.12.0-aikido.6","v1.11.0-aikido.1"],"sources":["osv"]},{"ecosystem":"Root:Go","package":"rootio-github.com/rabbitmq/amqp091-go","fixed_in":["v1.10.0-root.io.3","v1.10.0-root.io.4","v1.10.0-root.io.5","v1.10.0-root.io.6","v1.10.0-root.io.7","v1.12.0-root.io.2","v1.12.0-root.io.3","v1.12.0-root.io.4","v1.12.0-root.io.5","v1.12.0-root.io.6","v1.11.0-root.io.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"keda","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.14.1-19"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"telegraf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.31.0-34"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.10.0-1","1.11.0-1","1.12.0-1","1.14.0-1","1.15.0-1","1.5.0-2","1.8.1-1","1.8.1-2","1.9.0-1"]},{"source":"osv","ecosystem":"Debian:13","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.10.0-1","1.11.0-1","1.12.0-1","1.14.0-1","1.15.0-1"]},{"source":"osv","ecosystem":"Debian:14","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.14.0-1"}]}],"versions":["1.10.0-1","1.11.0-1","1.12.0-1"]},{"source":"osv","ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"opentelemetry-collector-contrib","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.161.0-0.1.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Root:Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v1.10.0-aikido.3"},{"fixed":"v1.10.0-aikido.4"},{"fixed":"v1.10.0-aikido.5"},{"fixed":"v1.10.0-aikido.6"},{"fixed":"v1.10.0-aikido.7"},{"fixed":"v1.12.0-aikido.2"},{"fixed":"v1.12.0-aikido.3"},{"fixed":"v1.12.0-aikido.4"},{"fixed":"v1.12.0-aikido.5"},{"fixed":"v1.12.0-aikido.6"},{"fixed":"v1.11.0-aikido.1"}]}]},{"source":"osv","ecosystem":"Root:Go","package":"rootio-github.com/rabbitmq/amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v1.10.0-root.io.3"},{"fixed":"v1.10.0-root.io.4"},{"fixed":"v1.10.0-root.io.5"},{"fixed":"v1.10.0-root.io.6"},{"fixed":"v1.10.0-root.io.7"},{"fixed":"v1.12.0-root.io.2"},{"fixed":"v1.12.0-root.io.3"},{"fixed":"v1.12.0-root.io.4"},{"fixed":"v1.12.0-root.io.5"},{"fixed":"v1.12.0-root.io.6"},{"fixed":"v1.11.0-root.io.1"}]}]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.8.1-2","1.9.0-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.10.0-1","1.11.0-1","1.12.0-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.10.0-1"]}],"products":[{"vendor":"rabbitmq","product":"amqp091-go"}],"references":[{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-r9c8-gcjp-xfwh","tags":["x_refsource_CONFIRM","advisory","web","article","report"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/346","tags":["x_refsource_MISC","fix","web","article","report"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/91b65fa0096a99a580cf51a31b24028ff1c60382","tags":["x_refsource_MISC","fix","web","article","report"]},{"url":"https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0","tags":["x_refsource_MISC","web","article"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77410","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-r9c8-gcjp-xfwh"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77410.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-77410","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go","tags":["package"]},{"url":"https://access.redhat.com/errata/RHSA-2026:68290","tags":["advisory"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-81872","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77404","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77412","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77403","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77410","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77409","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77406","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77407","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-93450","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-63209","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_68290.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2543236","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-63209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63209","tags":["advisory"]},{"url":"https://github.com/klauspost/compress/commit/539243b8823ee8f03e49969823d57c348c917536","tags":["article"]},{"url":"https://github.com/klauspost/compress/releases/tag/v1.18.7","tags":["article"]},{"url":"https://github.com/klauspost/compress/security/advisories/GHSA-259r-337f-4rfw","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77403","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/2e0a919b89f337dbf58db2bb34ab206dac354a06","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/353","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-xwwf-m8fg-p9q2","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535489","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77404","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/743d488e46955fe7ffc55506fe2c401d01216783","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/352","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-465g-fh3v-9jw4","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535493","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77406","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/3b879e1d1d25b544e26b3bc3d7db3213203c0f3b","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/351","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-rm6m-hrcw-jw33","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535487","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77407","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/fa013b8447eb60988db3c9281ff6b981e4d2fb4f","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/350","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-27gv-rfvv-22mv","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535494","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77409","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77409","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/5b0ccbb8d7bc3dfa18129d9b0f9256d656809494","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/349","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-wxx3-cj7g-w73j","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77410","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535499","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77412","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/669b42bf7b1db76bc6d4973e3634247f680accbf","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/344","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-4v58-74mf-rjx3","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535727","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-81872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81872","tags":["advisory"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/commit/ba71b09e6ed272e93a669aeaec1e98b1df4cc582","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/issues/6797","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/pull/8620","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/log/v0.21.0","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hjf4-fphr-2h65","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2538979","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93450","tags":["advisory"]},{"url":"https://github.com/go-openapi/swag","tags":["article"]},{"url":"https://github.com/go-openapi/swag/blob/v0.27.0/jsonutils/adapters/stdlib/json/adapter.go#L68","tags":["article"]},{"url":"https://github.com/go-openapi/swag/blob/v0.27.0/jsonutils/adapters/stdlib/json/ordered_map.go#L214","tags":["article"]},{"url":"https://github.com/go-openapi/swag/commit/0c24346ced59a25811e8694a915e7131d25ccb0e","tags":["article"]},{"url":"https://github.com/go-openapi/swag/security/advisories/GHSA-xh24-9qpg-8w28","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/go-openapi-swag-jsonutils-before-0.27.1-uncontrolled-recursion-in-ordered-json-marshal-and-unmarshal","tags":["article"]},{"url":"https://ubuntu.com/security/CVE-2026-77410","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-77410","title":"RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T14:39:08.872Z","modified":"2026-09-16T15:41:15.593Z","cvss":[{"version":"4.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","level":"high","assessor":"cna"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T14:20:15.712761Z"}],"euvd":[{"id":"EUVD-2026-80810","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T14:39:08Z","modified":"2026-09-16T15:41:15Z","cvss":[{"version":"4.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","level":"high"}],"updated_at":"2026-11-02T17:28:15.407859Z"}],"ghsa":[{"id":"GHSA-r9c8-gcjp-xfwh","title":"RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation","description":"**Summary**\nA flaw in the `recvContent` function allows a malicious AMQP server to trigger an Out-of-Memory (OOM) error, forcing the host operating system or container runtime to immediately terminate the client process.\n\n**Vulnerability Details**\nWhen receiving message content payloads, the client processes the expected size from the content header framework. The `recvContent` function attempts to optimize performance by pre-allocating memory for the message body based on the `ch.header.Size` field, which is a 64-bit unsigned integer (`uint64`).\n\n```go\n// channel.go:495-496\nif cap(ch.body) == 0 {\n    ch.body = make([]byte, 0, ch.header.Size)  // unbounded\n}\n```\n\nThe underlying library fails to validate or cap this requested size against any upper boundary—such as the maximum frame size negotiated during connection establishment (`FrameMax`). If a server specifies an extreme body size (e.g., `2^62` bytes), the Go runtime attempts to allocate an exabyte-scale slice capacity. This immediately exhausts available system memory, causing the operating system's OOM killer to terminate the application.\n\n**Attack Vector / Exploitation Scenario**\n\n- Message Delivery Phase: A malicious or compromised AMQP broker sends a standard `basic.deliver` frame containing a content header with an intentionally inflated `body-size` variable.\n- Authentication Requirement: No special privileges or authentication bypasses are required; the crash occurs seamlessly during normal message consumption.\n\n**Impact**\n\n- Availability: High. Exploded memory consumption results in an instant process termination, destroying application state and availability for all threads sharing the environment.","status":"published","published":"2026-09-17T17:04:20Z","modified":"2026-09-17T17:04:22Z","cvss":[{"version":"4.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","level":"high"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T14:41:18.357514Z"}],"nvd":[{"id":"CVE-2026-77410","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T15:17:50.43Z","modified":"2026-09-23T18:19:19.803Z","cvss":[{"version":"4.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T14:12:48.630594Z"}],"osv":[{"id":"CVE-2026-77410","title":"RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T14:39:08.872Z","modified":"2026-10-28T02:30:21.678037353Z","cvss":[{"version":"4.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","level":"high"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T15:45:17.102988Z"},{"id":"DEBIAN-CVE-2026-77410","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T15:17:50.43Z","modified":"2026-09-24T08:47:33.76085243Z","cvss":[{"version":"4.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"}],"updated_at":"2026-11-02T15:46:03.502256Z"},{"id":"GHSA-r9c8-gcjp-xfwh","title":"RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation","description":"**Summary**\nA flaw in the `recvContent` function allows a malicious AMQP server to trigger an Out-of-Memory (OOM) error, forcing the host operating system or container runtime to immediately terminate the client process.\n\n**Vulnerability Details**\nWhen receiving message content payloads, the client processes the expected size from the content header framework. The `recvContent` function attempts to optimize performance by pre-allocating memory for the message body based on the `ch.header.Size` field, which is a 64-bit unsigned integer (`uint64`).\n\n```go\n// channel.go:495-496\nif cap(ch.body) == 0 {\n    ch.body = make([]byte, 0, ch.header.Size)  // unbounded\n}\n```\n\nThe underlying library fails to validate or cap this requested size against any upper boundary—such as the maximum frame size negotiated during connection establishment (`FrameMax`). If a server specifies an extreme body size (e.g., `2^62` bytes), the Go runtime attempts to allocate an exabyte-scale slice capacity. This immediately exhausts available system memory, causing the operating system's OOM killer to terminate the application.\n\n**Attack Vector / Exploitation Scenario**\n\n- Message Delivery Phase: A malicious or compromised AMQP broker sends a standard `basic.deliver` frame containing a content header with an intentionally inflated `body-size` variable.\n- Authentication Requirement: No special privileges or authentication bypasses are required; the crash occurs seamlessly during normal message consumption.\n\n**Impact**\n\n- Availability: High. Exploded memory consumption results in an instant process termination, destroying application state and availability for all threads sharing the environment.","status":"published","published":"2026-09-17T17:04:20Z","modified":"2026-10-01T20:56:22.805183146Z","cvss":[{"version":"4.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","level":"high"}],"cwes":["CWE-789"],"updated_at":"2026-11-02T15:46:55.480549Z"},{"id":"RHSA-2026:68290","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update","status":"published","published":"2026-09-22T10:19:11Z","modified":"2026-10-20T10:43:37.203533689Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:22.406388Z"},{"id":"UBUNTU-CVE-2026-77410","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T15:17:00Z","modified":"2026-10-28T20:15:22.897835556Z","cvss":[{"version":"4.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","level":"high"}],"updated_at":"2026-11-02T16:57:18.015985Z"},{"id":"AZL-103185","title":"CVE-2026-77410 affecting package keda 2.14.1-19","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T15:17:50Z","modified":"2026-10-31T05:32:45Z","updated_at":"2026-11-02T15:28:00.794214Z"},{"id":"AZL-103299","title":"CVE-2026-77410 affecting package telegraf for versions less than 1.31.0-34","description":"RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.","status":"published","published":"2026-09-16T15:17:50Z","modified":"2026-11-02T14:15:30.93923532Z","updated_at":"2026-11-02T15:28:00.794214Z"},{"id":"GO-2026-6500","title":"RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation in github.com/rabbitmq/amqp091-go","description":"RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation in github.com/rabbitmq/amqp091-go","status":"published","published":"2026-10-01T20:23:56Z","modified":"2026-10-01T20:45:11.275893019Z","updated_at":"2026-11-02T15:47:03.11707Z"},{"id":"ROOT-APP-GOBINARY-CVE-2026-77410","title":"CVE-2026-77410 in github.com/rabbitmq/amqp091-go - Patched by Root","description":"Root has patched CVE-2026-77410 in the github.com/rabbitmq/amqp091-go package for Root:Go. Multiple fixed versions available.","status":"published","published":"2026-10-20T12:55:23Z","modified":"2026-10-20T13:15:04.109390503Z","updated_at":"2026-11-02T15:53:26.76659Z"}]}}