Most recent entries from all

CLEANSTART-2026-KZ39555 — Security fix for CVE-2026-79921 applied in: keda 2.17.2-r2, keda 2.20.2-r2, opentelemetry-collector-contrib 0.157.0-r1

Affected: CleanStart: keda, CleanStart: opentelemetry-collector-contrib

CVE-2026-79921 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.

EUVD-2026-361509

fkie_cve-2026-79921

amqp091-go is a Go AMQP 0.9.1 client. Before version 1.13.0, a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints. Version 1.13.0 contains a fix. No known workarounds are available.

GHSA-6c5v-hqjr-5xxp — amqp091-go has a Potential Memory Exhaustion/Protocol Violation via Broker-Controlled Oversized Payload

Affected: Go: github.com/rabbitmq/amqp091-go

**Summary** A vulnerability exists in the amqp091-go client library where a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints.

**Details** During a standard AMQP 0-9-1 connection handshake, the client and the broker negotiate a maximum frame size (frame_max), for example, 4096 bytes.

However, after negotiation, a malicious broker can send a valid basic.deliver sequence containing a content body frame whose header declares a payload size larger than the negotiated frame_max. Instead of enforcing the agreed-upon limit and closing the connection with a frame-error (as mandated by the AMQP 0-9-1 specification), the amqp091-go client:

1. Accepts the broker-declared oversized frame size. 2. Allocates memory based on this oversized declaration. 3. Reads the payload, assembles it into the message, and delivers it to the consumer.

**Impact**

- Denial of Service (DoS): If a broker sends extremely large frame sizes, it can trigger significant memory allocations on the client side, potentially leading to Out-Of-Memory (OOM) crashes. - Protocol Violation: The client fails to enforce negotiated connection parameters, trusting the broker implicitly even after constraints have been established.

RHSA-2026:60854 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

github.com/rabbitmq/amqp091-go: amqp091-go: Denial of Service via oversized AMQP payloads

UBUNTU-CVE-2026-79921

Affected: Ubuntu:24.04:LTS: golang-github-rabbitmq-amqp091-go, Ubuntu:26.04:LTS: golang-github-rabbitmq-amqp091-go