github.com/rabbitmq/amqp091-go
Affected
- introduced
0, fixed1.13.0(semver)
Fixed versions
1.13.0
Fix
- Fixed version
1.13.0go get github.com/rabbitmq/[email protected]
Advisory
Also known as: CVE-2026-77407, GO-2026-6491
RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields
Summary
An information disclosure vulnerability exists in the AMQP client implementation's authentication handling configuration. Following a successful connection handshake, the Connection.Config.SASL field stores the Authentication implementation state used to establish the session.
For standard PLAIN authentication, this state utilizes the PlainAuth struct, which defines both Username and Password as publicly exported, plaintext string fields. Because this sensitive data is retained permanently in-memory within an exported field structure, any peripheral code, internal package, reflective logger, dependency, or automated debugging utility with access to the core *Connection object can read and expose the raw credentials.
---
Vulnerability Details
Mechanism
The vulnerability stems from the structural design of the configuration storage used during and after the AMQP handshake:
// auth.go:21-23
type PlainAuth struct {
Username string
Password string // exported plaintext
}
When an application initializes a connection, the PlainAuth object is deeply nested inside the configuration structure (Connection.Config). Even after the handshake concludes and authentication is complete, this structure persists natively in-memory for the duration of the network connection's lifecycle.
Because Password is an exported string field, standard automated inspection mechanisms can read its value without restriction.
Affected Code Paths & Integrations
Any sub-component or library that traverses or reads the *Connection object will inadvertently read the plaintext password, including:
Impact
The credential remains vulnerable to leak paths into logging pipelines, log aggregators, security information and event management (SIEM) systems, or standard output. Once transmitted to external log infrastructure, these credentials become accessible to unprivileged operators or any actor with access to log archives.
---
Attack Vector
An attacker does not necessarily need direct remote code execution to exploit this flaw; instead, the vulnerability acts as a credential harvesting vector inside multi-tenant environments or via secondary log exposure:
*Connection object.reflect package to walk the structural hierarchy, pulling the string value from Connection.Config.SASL.(*PlainAuth).Password.High Basis: The source's own band: HIGH
0, fixed 1.13.0 (semver)1.13.0
1.13.0go get github.com/rabbitmq/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0