Live › vulnerability › CVE-2026-77404
Go to dashboardThe amqp091-go Go client builds AMQPS connection URIs by concatenating TLS file paths and server name into the query string without encoding them. If an application passes such a value into the URI and later parses it back with ParseURI, extra ampersand or equals characters can add or overwrite connection options.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/rabbitmq/amqp091-go | go | < 1.13.0 | 1.13.0 |
Unknown from the sources.
Upgrade github.com/rabbitmq/amqp091-go to 1.13.0 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, URI.String in uri.go concatenates CertFile, KeyFile, CACertFile, and ServerName values directly into an AMQPS query string instead of encoding them as URL query parameters with url.Values. If an application accepts a TLS asset path containing ampersand or equals delimiters and later reparses the serialized URI with ParseURI, the embedded delimiters can create or overwrite connection options, including paths to TLS certificate, key, or CA files. This can corrupt connection configuration or select unintended local cryptographic assets. This issue is fixed in version 1.13.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-77404")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.