RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, PlainAuth values defined in auth.go retain passwords as exported plaintext fields in Connection.Config.SASL after a successful PLAIN authentication handshake. The Connection.openComplete method in connection.go does not clear those values. Code with access to the Connection object, including reflective loggers, application performance monitoring agents, debugging utilities, and panic handlers, can traverse the configuration and expose the credentials to logs or state captures. The credential remains available for the lifetime of the connection instead of being cleared after authentication. This issue is fixed in version 1.13.0.
CVE-2026-77407
This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.0
- EG Score
- 7.0(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity70% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 16, 2026Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields · Advisory · rabbitmq/amqp091-go · GitHub
https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-27gv-rfvv-22mvv1.13.0
Patch available: rabbitmq/amqp091-go v1.13.0
https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0fix: redact and zero out plaintext SASL credentials after handshake
Patch available: rabbitmq/amqp091-go v1.13.0 (PR #350 merged 2026-06-18)
https://github.com/rabbitmq/amqp091-go/pull/350commit fa013b8447eb (rabbitmq/amqp091-go)
Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit fa013b8447eb)
https://github.com/rabbitmq/amqp091-go/commit/fa013b8447eb60988db3c9281ff6b981e4d2fb4fVendor Advisories for CVE-2026-77407(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:30 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 06:53 UTCEG score recompute
- 2026-09-16 15:20 UTCEG score recompute
- 2026-09-16 15:06 UTCEG score recompute
- 2026-09-16 14:46 UTCEG score recompute
- 2026-09-16 14:45 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-77407?
When was CVE-2026-77407 disclosed?
Is CVE-2026-77407 actively exploited?
What is the CVSS score of CVE-2026-77407?
How do I remediate CVE-2026-77407?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77407
Is Your Infrastructure Affected by CVE-2026-77407?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.