RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQP 0-9-1 is the most widely used protocol, and any publisher can trigger this condition. Preconditions include Any authenticated AMQP 0-9-1 client with publish permission can exploit this.. This issue is fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-770"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67235.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.11"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.20"
},
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.15"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
]
}{
"extracted_events": [
{
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.6"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"original_tag": "v4.2.6",
"range": [
{
"fixed": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
}
],
"source": "REFERENCES_TAG"
},
{
"original_tag": "v4.3.0",
"range": [
{
"fixed": "1929eeadf9b2bac12c5434fb56884ef27370580e"
}
],
"source": "REFERENCES_TAG"
}
]
}