CVE-2026-77404: RabbitMQ amqp091-go Connection Configuration Overwrite Vulnerability
HIGHCVE-2026-77404 is a HIGH connection configuration overwrite vulnerability (CWE-116: Improper Encoding or Escaping of Output) affecting RabbitMQ amqp091-go libraries in the Go ecosystem. The issue involves connection configuration overwrite via unsanitized tls path parameter injection. Remediation is available by upgrading affected packages to version 1.13.0.
CVE-2026-77404 at a Glance
How to Fix CVE-2026-77404
To remediate this vulnerability, upgrade all affected RabbitMQ amqp091-go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/rabbitmq/amqp091-go to 1.13.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/rabbitmq/amqp091-go
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-77404, inspect your project dependencies for RabbitMQ amqp091-go:
inspect dependencies for github.com/rabbitmq/amqp091-go
Analyze the terminal output to locate any version of RabbitMQ amqp091-go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.13.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-116: Improper Encoding or Escaping of Output, where the product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. as a result, the intended structure of the message is not preserved. In RabbitMQ amqp091-go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-77404 Affected RabbitMQ amqp091-go Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/rabbitmq/amqp091-go
|
Go |
< 1.13.0
|
1.13.0
|
References
Frequently Asked Questions
What is CVE-2026-77404?
Which RabbitMQ amqp091-go versions are affected?
What version fixes CVE-2026-77404?
Is github.com/rabbitmq/amqp091-go affected?
What CWE is associated with CVE-2026-77404?
How can I check Go dependencies for CVE-2026-77404?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-465g-fh3v-9jw4",
"modified" : "2026-09-17T17:03:55Z",
"published" : "2026-09-17T17:03:55Z",
"aliases" : [ "CVE-2026-77404" ],
"summary" : "RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection",
"details" : "## Summary\nA query parameter injection vulnerability exists in the AMQP client's connection URI formatting logic. When generating or parsing connection URIs, TLS-related filesystem paths (such as certificates or keys) are appended directly to the URI's query string using string concatenation rather than secure URL encoding via functions like `url.QueryEscape`.\n\nIf an application handles a TLS file path containing special character delimiters (such as `&` or `=`), these characters are interpreted as parameter separators by the URI parser. If the resulting `URI.String()` output is subsequently re-parsed via `ParseURI`, the injected fields can silently overwrite or hijack critical configuration parameters, forcing the client to use arbitrary connection settings or alternate TLS files.\n\n---\n\n## Vulnerability Details\n\n### Mechanism\nThe vulnerability lies within the lack of proper escaping when compiling connection string components into a raw URL format:\n\n```go\n// Example of insecure string concatenation during URI building\nuri := fmt.Sprintf(\"amqps://user:pass@host/%s?certfile=%s&keyfile=%s\", vhost, certPath, keyPath)\n```\n\nBecause `certPath` and `keyPath` are not passed through `url.QueryEscape`, special URL characters preserve their control meanings. For instance, if a user supply a certificate path named:\n`/tmp/cert=foo&keyfile=/evil/path`\n\nThe generated string translates into:\n`...?certfile=/tmp/cert=foo&keyfile=/evil/path&keyfile=/original/path`\n\nWhen this string passes back through `ParseURI` (common in connection re-dial routines or configuration replication steps), standard URL parsing mechanics treat the string as multiple distinct parameters. Depending on map assignment order inside the parser, the injected keys take precedence over the original parameters.\n\n### Impact\nBy manipulating the file paths used for TLS assets, an attacker or compromised local sub-system can:\n* Inject arbitrary alternative options or override protocol settings.\n* Substitute or switch keyfiles, leading to connection failures or the parsing of unauthorized cryptographic assets.\n* Corrupt connection state variables, triggering application-layer failures during connection setup or recovery.\n\n---\n\n## Attack Vector\nAn attacker who has partial control over directory naming conventions or environmental variables used to specify local infrastructure paths can execute a parameter injection attack:\n\n1. **Path Creation:** An attacker sets up a path containing deliberate URL parameter delimiters (e.g., `/var/lib/certs/client.crt?cacertfile=/tmp/fake_ca.crt&`).\n2. **String Generation:** The application serializes the active connection state or passes the paths down to an unescaped URI builder function.\n3. **Configuration Hijack:** The URI string is generated with the injected parameter embedded into the query structure. When the client attempts to reuse or re-parse this connection string during a connection retry or worker spin-up, it parses the injected `cacertfile` parameter, loading a different, unverified Certificate Authority string.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/rabbitmq/amqp091-go"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.13.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-465g-fh3v-9jw4"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-77404"
}, {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/amqp091-go/pull/352"
}, {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/amqp091-go/commit/743d488e46955fe7ffc55506fe2c401d01216783"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/rabbitmq/amqp091-go"
}, {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-116" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-17T17:03:55Z",
"nvd_published_at" : "2026-09-16T15:17:47Z"
}
}