RabbitMQ: Stream-protocol frame length never validated against frame_max
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
- Products
- rabbitmq
- Affected versions
- Not specified
- Fixed versions
- 3.13.15, 4.0.20, 4.1.11, 4.2.6
- CVEs
- CVE-2026-67225
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 14:09 UTC · Revision 1
Source evidence
RabbitMQ: Stream-protocol frame length never validated against frame_max
core-osv · Original sourcePublished 1 Oct 2026, 09:33 UTC
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
osv:BIT-rabbitmq-2026-67225
rabbitmq
Fixed versions: 3.13.15, 4.0.20, 4.1.11, 4.2.6
Complete source record
{
"id": "bc33eca174831f3cd309adfd4e259ed243ae956cbc1637e0c78074cc9ae33f86",
"url": "https://osv.dev/vulnerability/BIT-rabbitmq-2026-67225",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ: Stream-protocol frame length never validated against frame_max",
"summary": "RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.",
"evidence": "osv:BIT-rabbitmq-2026-67225",
"products": [
{
"name": {
"value": "rabbitmq",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.13.15",
"evidence": "/affected/0/ranges"
},
{
"value": "4.0.20",
"evidence": "/affected/0/ranges"
},
{
"value": "4.1.11",
"evidence": "/affected/0/ranges"
},
{
"value": "4.2.6",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "BIT-rabbitmq-2026-67225",
"aliases": [
"BIT-rabbitmq-2026-67225",
"CVE-2026-67225",
"GHSA-c8c4-gvv4-8j3q"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.15"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.20"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.11"
},
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.6"
}
]
}
],
"package": {
"name": "rabbitmq",
"purl": "pkg:bitnami/rabbitmq",
"ecosystem": "Bitnami"
},
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"database_specific": {
"source": "https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-67225.json"
}
}
],
"modified": "2026-10-21T12:00:38.491449467Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-c8c4-gvv4-8j3q",
"https://nvd.nist.gov/vuln/detail/CVE-2026-67225"
],
"provider_metadata": {
"cpes": [
"cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
],
"severity": "High"
}
},
"related_cves": [
{
"value": "CVE-2026-67225",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 393021,
"published_at": "2026-10-01T09:33:15.158+00:00"
}