Most recent entries from all

CLEANSTART-2026-AD74285 — RabbitMQ amqp091-go is a Go AMQP 0

Affected: CleanStart: opentelemetry-collector-contrib

Security vulnerability affects the opentelemetry-collector-contrib package. RabbitMQ amqp091-go is a Go AMQP 0.

EUVD-2026-372225

fkie_cve-2026-77405

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, tlsConfigFromURI in uri.go creates tls.Config values without setting MinVersion to tls.VersionTLS12. Builds using a Go runtime whose default permits TLS 1.0 or TLS 1.1 can therefore negotiate an obsolete protocol version when connecting through an amqps URI. A network attacker able to influence TLS negotiation with such a legacy build may weaken transport protection for AMQP messages and credentials. This issue is fixed in version 1.13.0.

GHSA-33mj-cw25-m34h — RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser

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

## Summary A structural security weakness exists in the AMQP client's TLS configuration generator (`tlsConfigFromURI`). When constructing a `*tls.Config` object from an `amqps://` connection URI, the library initializes the structure without explicitly defining the `MinVersion` field.

While modern versions of the Go compiler toolchain (Go 1.18+) default the implicit minimum version to TLS 1.2, this security posture relies entirely on an implicit toolchain dependency. If the library is compiled using legacy Go toolchains (Go < 1.18), or if a future toolchain introduces fallback behavior, the client could silently negotiate obsolete and insecure TLS 1.0 or TLS 1.1 protocols during connection handshakes with a compromised or malicious AMQP broker.

---

## Vulnerability Details

### Mechanism The vulnerability lies in the lack of an explicit safety floor when assigning configurations inside the URI component:

```go // Example within uri.go's tlsConfigFromURI cfg := &tls.Config{ ServerName: host, // MinVersion is left completely unassigned (defaults to 0, or toolchain default) } ```

In the Go standard library (`crypto/tls`), leaving `MinVersion: 0` instructs the runtime to choose the toolchain's default minimum. Prior to Go 1.18, this default allowed negotiation down to TLS 1.0. Relying on implicit compiler configurations violates secure coding practices by decoupling the library's security posture from its source code, leaving applications vulnerable based solely on…

msrc_CVE-2026-77405 — RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser

msrc_CVE-2026-77405