ubuntu-cve-2026-61634
Vulnerability from osv_ubuntu
The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, the AMQP connection tuning path records the negotiated AMQP frame_max value, but src/main/java/com/rabbitmq/client/impl/SocketFrameHandler.java and NettyFrameHandlerFactory continue to validate broker-controlled frame payload lengths against maxInboundMessageBodySize because the negotiated limit is not applied consistently through setMaxInboundFramePayloadSize. A malicious or compromised broker can send a method frame larger than the negotiated frame_max during or after connection establishment, causing the client to allocate and decode a protocol-invalid frame instead of rejecting it with MalformedFrameException. The protocol violation can disrupt the affected connection and cause client-side denial of service. This issue is fixed in version 5.33.0.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librabbitmq-client-java",
"binary_version": "5.0.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "rabbitmq-java-client",
"purl": "pkg:deb/ubuntu/rabbitmq-java-client@5.0.0-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librabbitmq-client-java",
"binary_version": "5.0.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "rabbitmq-java-client",
"purl": "pkg:deb/ubuntu/rabbitmq-java-client@5.0.0-1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librabbitmq-client-java",
"binary_version": "5.0.0-1.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "rabbitmq-java-client",
"purl": "pkg:deb/ubuntu/rabbitmq-java-client@5.0.0-1.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librabbitmq-client-java",
"binary_version": "5.0.0-1.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "rabbitmq-java-client",
"purl": "pkg:deb/ubuntu/rabbitmq-java-client@5.0.0-1.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "librabbitmq-client-java",
"binary_version": "5.0.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "rabbitmq-java-client",
"purl": "pkg:deb/ubuntu/rabbitmq-java-client@5.0.0-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1.1",
"5.0.0-2"
]
}
],
"aliases": [],
"details": "The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, the AMQP connection tuning path records the negotiated AMQP frame_max value, but src/main/java/com/rabbitmq/client/impl/SocketFrameHandler.java and NettyFrameHandlerFactory continue to validate broker-controlled frame payload lengths against maxInboundMessageBodySize because the negotiated limit is not applied consistently through setMaxInboundFramePayloadSize. A malicious or compromised broker can send a method frame larger than the negotiated frame_max during or after connection establishment, causing the client to allocate and decode a protocol-invalid frame instead of rejecting it with MalformedFrameException. The protocol violation can disrupt the affected connection and cause client-side denial of service. This issue is fixed in version 5.33.0.",
"id": "UBUNTU-CVE-2026-61634",
"modified": "2026-09-02T16:20:05Z",
"published": "2026-08-18T17:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-61634"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-61634"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-61634"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.