amqp091-go: Pre-negotiation frame limit is not enforced to 4KB
## Summary The frame-size mitigation released in `amqp091-go` v1.13.0 can be bypassed before `connection.tune` completes. A malicious or compromised AMQP peer can send only a seven-byte body-frame header containing a large attacker-controlled `uint32` payload length. The client allocates a slice of that declared length before it verifies that the payload exists or rejects the frame for its invalid protocol state. The bypass occurs because `Connection.maxFrameSize` starts at zero. The reader interprets zero as both “negotiated unlimited” and “not negotiated yet,” and skips the pre-allocation size check in either case. `Open` starts the reader goroutine before negotiation and does not store a limit until after it receives `connection.tune`. This remains reachable even if the caller explicitly uses `Config{FrameSize: frameMinSize}`. A malicious broker can therefore cause excessive memory allocation, potentially terminating the Go client process through memory exhaustion, before authentication and connection setup complete. ## Relationship to the existing advisory [GHSA-r9c8-gcjp-xfwh](https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-r9c8-gcjp-xfwh) describes attacker-controlled, unbounded allocation by a malicious broker and identifies v1.13.0 as the patched version. [Pull request 369](https://github.com/rabbitmq/amqp091-go/pull/369) added a frame-size check before parser allocation, but the check is active only when the stored maximum is nonzero. The v1.13.0 sour
- Products
- github.com/rabbitmq/amqp091-go
- Affected versions
- Not specified
- Fixed versions
- 1.14.0
- CVEs
- CVE-2026-107386
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 08:44 UTC · Revision 1
Source evidence
amqp091-go: Pre-negotiation frame limit is not enforced to 4KB
core-osv · Original sourcePublished 8 Oct 2026, 19:40 UTC
## Summary The frame-size mitigation released in `amqp091-go` v1.13.0 can be bypassed before `connection.tune` completes. A malicious or compromised AMQP peer can send only a seven-byte body-frame header containing a large attacker-controlled `uint32` payload length. The client allocates a slice of that declared length before it verifies that the payload exists or rejects the frame for its invalid protocol state. The bypass occurs because `Connection.maxFrameSize` starts at zero. The reader interprets zero as both “negotiated unlimited” and “not negotiated yet,” and skips the pre-allocation size check in either case. `Open` starts the reader goroutine before negotiation and does not store a limit until after it receives `connection.tune`. This remains reachable even if the caller explicitly uses `Config{FrameSize: frameMinSize}`. A malicious broker can therefore cause excessive memory allocation, potentially terminating the Go client process through memory exhaustion, before authentication and connection setup complete. ## Relationship to the existing advisory [GHSA-r9c8-gcjp-xfwh](https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-r9c8-gcjp-xfwh) describes attacker-controlled, unbounded allocation by a malicious broker and identifies v1.13.0 as the patched version. [Pull request 369](https://github.com/rabbitmq/amqp091-go/pull/369) added a frame-size check before parser allocation, but the check is active only when the stored maximum is nonzero. The v1.13.0 sour
osv:GHSA-w6r9-248c-frg8
github.com/rabbitmq/amqp091-go
Fixed versions: 1.14.0
Complete source record
{
"id": "cc0b95067f24fe5de65e60e47de8ad01a7f9099198317c0f4548ba8d04144607",
"url": "https://osv.dev/vulnerability/GHSA-w6r9-248c-frg8",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "amqp091-go: Pre-negotiation frame limit is not enforced to 4KB",
"summary": "## Summary The frame-size mitigation released in `amqp091-go` v1.13.0 can be bypassed before `connection.tune` completes. A malicious or compromised AMQP peer can send only a seven-byte body-frame header containing a large attacker-controlled `uint32` payload length. The client allocates a slice of that declared length before it verifies that the payload exists or rejects the frame for its invalid protocol state. The bypass occurs because `Connection.maxFrameSize` starts at zero. The reader interprets zero as both “negotiated unlimited” and “not negotiated yet,” and skips the pre-allocation size check in either case. `Open` starts the reader goroutine before negotiation and does not store a limit until after it receives `connection.tune`. This remains reachable even if the caller explicitly uses `Config{FrameSize: frameMinSize}`. A malicious broker can therefore cause excessive memory allocation, potentially terminating the Go client process through memory exhaustion, before authentication and connection setup complete. ## Relationship to the existing advisory [GHSA-r9c8-gcjp-xfwh](https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-r9c8-gcjp-xfwh) describes attacker-controlled, unbounded allocation by a malicious broker and identifies v1.13.0 as the patched version. [Pull request 369](https://github.com/rabbitmq/amqp091-go/pull/369) added a frame-size check before parser allocation, but the check is active only when the stored maximum is nonzero. The v1.13.0 sour",
"evidence": "osv:GHSA-w6r9-248c-frg8",
"products": [
{
"name": {
"value": "github.com/rabbitmq/amqp091-go",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.14.0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "GHSA-w6r9-248c-frg8",
"aliases": [
"CVE-2026-107386",
"GHSA-w6r9-248c-frg8",
"GO-2026-6700"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.14.0"
}
]
}
],
"package": {
"name": "github.com/rabbitmq/amqp091-go",
"purl": "pkg:golang/github.com/rabbitmq/amqp091-go",
"ecosystem": "Go"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-w6r9-248c-frg8/GHSA-w6r9-248c-frg8.json"
}
}
],
"modified": "2026-10-19T21:41:15.822630367Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-w6r9-248c-frg8",
"https://github.com/rabbitmq/amqp091-go/pull/377",
"https://github.com/rabbitmq/amqp091-go/commit/6723e8cff8710f0a6bf5fb4af375e285052535b3",
"https://github.com/rabbitmq/amqp091-go",
"https://github.com/rabbitmq/amqp091-go/releases/tag/v1.14.0"
],
"provider_metadata": {
"cwe_ids": [
"CWE-770"
],
"severity": "MODERATE",
"github_reviewed": true,
"nvd_published_at": null,
"github_reviewed_at": "2026-10-08T19:40:19Z"
}
},
"related_cves": [
{
"value": "CVE-2026-107386",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 376789,
"published_at": "2026-10-08T19:40:19+00:00"
}Pre-negotiation frame limit is not enforced to 4KB in github.com/rabbitmq/amqp091-go
core-osv · Original sourcePublished 19 Oct 2026, 21:08 UTC
Pre-negotiation frame limit is not enforced to 4KB in github.com/rabbitmq/amqp091-go
osv:GO-2026-6700
github.com/rabbitmq/amqp091-go
Fixed versions: 1.14.0
Complete source record
{
"id": "1ef9b9793203bb65bf48cb66dd2bf95236c5bb6d358ef275375c941d5e4822b1",
"url": "https://osv.dev/vulnerability/GO-2026-6700",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Pre-negotiation frame limit is not enforced to 4KB in github.com/rabbitmq/amqp091-go",
"summary": "Pre-negotiation frame limit is not enforced to 4KB in github.com/rabbitmq/amqp091-go",
"evidence": "osv:GO-2026-6700",
"products": [
{
"name": {
"value": "github.com/rabbitmq/amqp091-go",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.14.0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "GO-2026-6700",
"aliases": [
"CVE-2026-107386",
"GHSA-w6r9-248c-frg8",
"GO-2026-6700"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.14.0"
}
]
}
],
"package": {
"name": "github.com/rabbitmq/amqp091-go",
"purl": "pkg:golang/github.com/rabbitmq/amqp091-go",
"ecosystem": "Go"
},
"database_specific": {
"source": "https://vuln.go.dev/ID/GO-2026-6700.json"
},
"ecosystem_specific": {
"imports": [
{
"path": "github.com/rabbitmq/amqp091-go",
"symbols": [
"Dial",
"DialConfig",
"DialTLS",
"DialTLS_ExternalAuth",
"Open"
]
}
]
}
}
],
"modified": "2026-10-19T21:31:49.521720293Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-w6r9-248c-frg8",
"https://github.com/rabbitmq/amqp091-go/commit/6723e8cff8710f0a6bf5fb4af375e285052535b3",
"https://github.com/rabbitmq/amqp091-go/pull/377",
"https://github.com/rabbitmq/amqp091-go/releases/tag/v1.14.0"
],
"provider_metadata": {
"url": "https://pkg.go.dev/vuln/GO-2026-6700",
"review_status": "REVIEWED"
}
},
"related_cves": [
{
"value": "CVE-2026-107386",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 376688,
"published_at": "2026-10-19T21:08:21+00:00"
}