RabbitMQ 4.3 hardened image update closes two unauthenticated denial-of-service paths
Red Hat’s August 21 build fixes HTTP/1.1, HTTP/2 and HTTP/3 parsing flaws that can exhaust memory without authentication.
Red Hat has issued an Important security update for the RabbitMQ 4.3 RPM in Red Hat Hardened Images. The August 21 advisory ships rabbitmq-server4.3-4.3.5-0.1.hum1 for x86_64 and aarch64 and addresses two remotely exploitable denial-of-service flaws.
What changed
The update covers CVE-2026-59248 and CVE-2026-65624. Red Hat rates both vulnerabilities Important with CVSS 3.1 base scores of 7.5. Each can be reached over the network without privileges or user interaction, and each can exhaust memory until the affected service becomes unavailable.
CVE-2026-59248 is in Cowlib’s HTTP parser. Specially crafted HTTP/2 or HTTP/3 frames can carry oversized HPACK or QPACK prefixed integers, triggering unbounded decoding, memory allocation and garbage collection. Red Hat says the result can be memory exhaustion on either a vulnerable server or client.
CVE-2026-65624 affects Cowboy’s handling of HTTP/1.1 headers. An attacker can submit repeated header lines with the same name to bypass the max_headers limit. Concatenating those values can then grow the connection process until the Erlang virtual machine runs out of memory.
Who is affected
The August 21 advisory applies specifically to the rabbitmq-server4-3-main component in Red Hat Hardened Images. Red Hat’s CVE records also show earlier fixes for RabbitMQ 4.2 and 4.3 hardened-image streams issued on July 28; the newer advisory supplies the listed RabbitMQ 4.3 build.
Both attack paths are remote and unauthenticated. Their impact is availability rather than confidentiality or integrity, but the absence of an authentication requirement lowers the barrier to triggering a service outage when a vulnerable endpoint is reachable.
What to do
Red Hat lists both issues as fixed by RHSA-2026:57882 and does not provide a mitigation that meets its deployment and stability criteria. Operators using the RabbitMQ 4.3 hardened image should identify deployments based on an older build and apply the updated image through Red Hat’s hardened-images service.
After rollout, teams should confirm that workloads resolve to the corrected 4.3.5-0.1.hum1 RPM build for their architecture. Because both flaws consume memory through malformed HTTP input, monitoring for abnormal RabbitMQ or Erlang memory growth can also help identify attempted exploitation while updates are being deployed.
sources
- RHSA-2026:57882 — Red Hat Hardened Images RPMs security updateaccess.redhat.com
- CVE-2026-59248access.redhat.com
- CVE-2026-65624access.redhat.com
comments · 0