{"id":"CVE-2026-77404","aliases":["DEBIAN-CVE-2026-77404","EUVD-2026-80817","GHSA-465g-fh3v-9jw4","GO-2026-6493","RHSA-2026:68290","ROOT-APP-GOBINARY-CVE-2026-77404","UBUNTU-CVE-2026-77404"],"status":"published","title":"RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection","description":"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.","severity":{"version":"4.0","score":8.7,"vector":"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","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00104,"percentile":0.01041,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-116"],"published":"2026-09-16T14:40:49Z","modified":"2026-10-28T02:30:53Z","fixes":[{"ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","fixed_in":["1.13.0"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:14","package":"golang-github-rabbitmq-amqp091-go","fixed_in":["1.14.0-1"],"sources":["osv"]},{"ecosystem":"Root:Go","package":"github.com/rabbitmq/amqp091-go","fixed_in":["v1.10.0-aikido.4","v1.10.0-aikido.5","v1.10.0-aikido.6","v1.10.0-aikido.7","v1.12.0-aikido.4","v1.12.0-aikido.5","v1.12.0-aikido.6","v1.11.0-aikido.1"],"sources":["osv"]},{"ecosystem":"Root:Go","package":"rootio-github.com/rabbitmq/amqp091-go","fixed_in":["v1.10.0-root.io.4","v1.10.0-root.io.5","v1.10.0-root.io.6","v1.10.0-root.io.7","v1.12.0-root.io.4","v1.12.0-root.io.5","v1.12.0-root.io.6","v1.11.0-root.io.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.10.0-1","1.11.0-1","1.12.0-1","1.14.0-1","1.15.0-1"]},{"source":"osv","ecosystem":"Debian:14","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.14.0-1"}]}],"versions":["1.10.0-1","1.11.0-1","1.12.0-1"]},{"source":"osv","ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"opentelemetry-collector-contrib","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.161.0-0.1.hum1"}]}],"bundled":10},{"source":"osv","ecosystem":"Root:Go","package":"github.com/rabbitmq/amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v1.10.0-aikido.4"},{"fixed":"v1.10.0-aikido.5"},{"fixed":"v1.10.0-aikido.6"},{"fixed":"v1.10.0-aikido.7"},{"fixed":"v1.12.0-aikido.4"},{"fixed":"v1.12.0-aikido.5"},{"fixed":"v1.12.0-aikido.6"},{"fixed":"v1.11.0-aikido.1"}]}]},{"source":"osv","ecosystem":"Root:Go","package":"rootio-github.com/rabbitmq/amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"v1.10.0-root.io.4"},{"fixed":"v1.10.0-root.io.5"},{"fixed":"v1.10.0-root.io.6"},{"fixed":"v1.10.0-root.io.7"},{"fixed":"v1.12.0-root.io.4"},{"fixed":"v1.12.0-root.io.5"},{"fixed":"v1.12.0-root.io.6"},{"fixed":"v1.11.0-root.io.1"}]}]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.8.1-2","1.9.0-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.10.0-1","1.11.0-1","1.12.0-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"golang-github-rabbitmq-amqp091-go","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.10.0-1"]}],"products":[{"vendor":"rabbitmq","product":"amqp091-go"}],"references":[{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-465g-fh3v-9jw4","tags":["x_refsource_CONFIRM","advisory","web","article","report"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/352","tags":["x_refsource_MISC","fix","web","article","report"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/743d488e46955fe7ffc55506fe2c401d01216783","tags":["x_refsource_MISC","fix","web","article","report"]},{"url":"https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0","tags":["x_refsource_MISC","web","article"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77404","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-465g-fh3v-9jw4"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77404.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-77404","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go","tags":["package"]},{"url":"https://access.redhat.com/errata/RHSA-2026:68290","tags":["advisory"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-81872","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77404","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77412","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77403","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77410","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77409","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77406","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77407","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-93450","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-63209","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_68290.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2543236","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-63209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63209","tags":["advisory"]},{"url":"https://github.com/klauspost/compress/commit/539243b8823ee8f03e49969823d57c348c917536","tags":["article"]},{"url":"https://github.com/klauspost/compress/releases/tag/v1.18.7","tags":["article"]},{"url":"https://github.com/klauspost/compress/security/advisories/GHSA-259r-337f-4rfw","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535498","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77403","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/2e0a919b89f337dbf58db2bb34ab206dac354a06","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/353","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-xwwf-m8fg-p9q2","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535489","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77404","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535493","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77406","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/3b879e1d1d25b544e26b3bc3d7db3213203c0f3b","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/351","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-rm6m-hrcw-jw33","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535487","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77407","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/fa013b8447eb60988db3c9281ff6b981e4d2fb4f","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/350","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-27gv-rfvv-22mv","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535494","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77409","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77409","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/5b0ccbb8d7bc3dfa18129d9b0f9256d656809494","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/349","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-wxx3-cj7g-w73j","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535500","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77410","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/91b65fa0096a99a580cf51a31b24028ff1c60382","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/346","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-r9c8-gcjp-xfwh","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535499","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77412","tags":["advisory"]},{"url":"https://github.com/rabbitmq/amqp091-go/commit/669b42bf7b1db76bc6d4973e3634247f680accbf","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/pull/344","tags":["article"]},{"url":"https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-4v58-74mf-rjx3","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535727","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-81872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81872","tags":["advisory"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/commit/ba71b09e6ed272e93a669aeaec1e98b1df4cc582","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/issues/6797","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/pull/8620","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/log/v0.21.0","tags":["article"]},{"url":"https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hjf4-fphr-2h65","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2538979","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93450","tags":["advisory"]},{"url":"https://github.com/go-openapi/swag","tags":["article"]},{"url":"https://github.com/go-openapi/swag/blob/v0.27.0/jsonutils/adapters/stdlib/json/adapter.go#L68","tags":["article"]},{"url":"https://github.com/go-openapi/swag/blob/v0.27.0/jsonutils/adapters/stdlib/json/ordered_map.go#L214","tags":["article"]},{"url":"https://github.com/go-openapi/swag/commit/0c24346ced59a25811e8694a915e7131d25ccb0e","tags":["article"]},{"url":"https://github.com/go-openapi/swag/security/advisories/GHSA-xh24-9qpg-8w28","tags":["article"]},{"url":"https://www.vulncheck.com/advisories/go-openapi-swag-jsonutils-before-0.27.1-uncontrolled-recursion-in-ordered-json-marshal-and-unmarshal","tags":["article"]},{"url":"https://ubuntu.com/security/CVE-2026-77404","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-77404","title":"RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection","description":"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.","status":"published","published":"2026-09-16T14:40:49.895Z","modified":"2026-09-16T15:21:51.197Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high","assessor":"cna"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T14:20:15.712761Z"}],"euvd":[{"id":"EUVD-2026-80817","description":"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.","status":"published","published":"2026-09-16T14:40:49Z","modified":"2026-09-16T15:21:51Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"updated_at":"2026-11-02T17:28:15.407859Z"}],"ghsa":[{"id":"GHSA-465g-fh3v-9jw4","title":"RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection","description":"## 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 `\u0026` 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\u0026keyfile=%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\u0026keyfile=/evil/path`\n\nThe generated string translates into:\n`...?certfile=/tmp/cert=foo\u0026keyfile=/evil/path\u0026keyfile=/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\u0026`).\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.","status":"published","published":"2026-09-17T17:03:55Z","modified":"2026-09-17T17:03:57Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T14:41:18.357514Z"}],"nvd":[{"id":"CVE-2026-77404","description":"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.","status":"published","published":"2026-09-16T15:17:47.067Z","modified":"2026-09-23T18:19:19.803Z","cvss":[{"version":"4.0","score":8.7,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T14:12:48.630594Z"}],"osv":[{"id":"CVE-2026-77404","title":"RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection","description":"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.","status":"published","published":"2026-09-16T14:40:49.895Z","modified":"2026-10-28T02:30:53.488890604Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T15:45:17.102988Z"},{"id":"DEBIAN-CVE-2026-77404","description":"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.","status":"published","published":"2026-09-16T15:17:47.067Z","modified":"2026-10-04T00:00:12.400167123Z","cvss":[{"version":"4.0","score":8.7,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"}],"updated_at":"2026-11-02T15:46:03.502256Z"},{"id":"GHSA-465g-fh3v-9jw4","title":"RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection","description":"## 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 `\u0026` 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\u0026keyfile=%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\u0026keyfile=/evil/path`\n\nThe generated string translates into:\n`...?certfile=/tmp/cert=foo\u0026keyfile=/evil/path\u0026keyfile=/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\u0026`).\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.","status":"published","published":"2026-09-17T17:03:55Z","modified":"2026-10-01T20:56:11.411656712Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T15:46:36.434231Z"},{"id":"RHSA-2026:68290","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update","status":"published","published":"2026-09-22T10:19:11Z","modified":"2026-10-20T10:43:37.203533689Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:22.406388Z"},{"id":"UBUNTU-CVE-2026-77404","description":"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.","status":"published","published":"2026-09-16T15:17:00Z","modified":"2026-10-17T13:01:08.242990175Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"updated_at":"2026-11-02T16:57:18.015985Z"},{"id":"GO-2026-6493","title":"RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection in github.com/rabbitmq/amqp091-go","description":"RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection in github.com/rabbitmq/amqp091-go","status":"published","published":"2026-10-01T20:23:56Z","modified":"2026-10-01T20:45:11.266820852Z","updated_at":"2026-11-02T15:47:03.11707Z"},{"id":"ROOT-APP-GOBINARY-CVE-2026-77404","title":"CVE-2026-77404 in github.com/rabbitmq/amqp091-go - Patched by Root","description":"Root has patched CVE-2026-77404 in the github.com/rabbitmq/amqp091-go package for Root:Go. Multiple fixed versions available.","status":"published","published":"2026-10-20T12:55:23Z","modified":"2026-10-20T13:15:03.031042709Z","updated_at":"2026-11-02T15:53:26.76659Z"}]}}