Is CVE-2026-77404 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-77404 being exploited in the wild.

How severe is CVE-2026-77404?

High severity, with a CVSS score of 4, published 16 September 2026.

Is there a fix for CVE-2026-77404?

Yes. github.com/rabbitmq/amqp091-go (Go): upgrade to 1.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-77404 attacked?

It is attacked with local access or from the adjacent network.

Am I affected by CVE-2026-77404?

Check whether you run github.com/rabbitmq/amqp091-go (Go) or RabbitMQ Amqp091-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-77404: RabbitMQ amqp091-go connection configuration injection via TLS path parameter

CVE-2026-77404 · Severity: high · CVSS 4 · Published 2026-09-16

The RabbitMQ Go AMQP client library fails to properly escape TLS certificate and key file paths when building connection strings. An attacker who can control the names of directories containing TLS files can inject malicious URL parameters that override critical connection settings, potentially forcing the client to use unauthorized certificates or alternate authentication credentials when connecting to RabbitMQ brokers.

Technologies: github.com/rabbitmq/amqp091-go (Go), RabbitMQ Amqp091-Go. Vendors: Go, RabbitMQ.

Quick answers

Is CVE-2026-77404 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-77404 being exploited in the wild.
How severe is CVE-2026-77404?: High severity, with a CVSS score of 4, published 16 September 2026.
Which products and versions are affected?: github.com/rabbitmq/amqp091-go (Go) < 1.13.0, SEMVER:introduced=0,fixed=1.13.0; RabbitMQ Amqp091-Go <UNKNOWN>.
Is there a fix for CVE-2026-77404?: Yes. github.com/rabbitmq/amqp091-go (Go): upgrade to 1.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-77404 attacked?: It is attacked with local access or from the adjacent network.
Am I affected by CVE-2026-77404?: Check whether you run github.com/rabbitmq/amqp091-go (Go) or RabbitMQ Amqp091-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/rabbitmq/amqp091-go (Go): upgrade to 1.13.0 or later
```
go get github.com/rabbitmq/amqp091-go@v1.13.0
```

Technical details

The vulnerability is a query parameter injection flaw in the AMQP 0.9.1 Go client's connection URI formatting logic. The root cause is unsafe string concatenation of TLS filesystem paths directly into URI query parameters without calling `url.QueryEscape()` to properly encode special characters. An attacker who can control TLS file paths (e.g., via directory naming) can craft paths containing URL delimiters like `&` and `=` that break out of their intended parameter and inject new query parameters. When such a malformed URI string is re-parsed via `ParseURI()` during connection retry or state serialization, the injected parameters silently overwrite original configuration values, allowing substitution of certificate files or other connection settings. The attack requires either local filesystem access to control directory names or influence over environment variables specifying TLS paths, but no authentication is required to exploit the injection itself.

Affected products

RabbitMQ amqp091-go <UNKNOWN>

Identifiers

CVE-2026-77404
GHSA-465g-fh3v-9jw4
GO-2026-6493

Timeline

2026-09-17: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.