BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-77407High confidence

RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields

rabbitmq · amqp091-go

Official source article: GitHub GHSA-27GV-RFVV-22MV ↗. Check the applicable product and release in the original source.

7.0HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 16 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs rabbitmq amqp091-go and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegolang-github-rabbitmq-amqp091-goAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 9 Oct 2026
Debian bookwormbookworm · sourcegolang-github-rabbitmq-amqp091-goAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 9 Oct 2026
Debian forkyforky · sourcegolang-github-rabbitmq-amqp091-goVendor fix publishedDebian records a fixed source-package version for this release.1.14.0-1Debian Security Tracker ↗Source updated 9 Oct 2026
Debian sidsid · sourcegolang-github-rabbitmq-amqp091-goVendor fix publishedDebian records a fixed source-package version for this release.1.14.0-1Debian Security Tracker ↗Source updated 9 Oct 2026
Open-source package ranges3 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/rabbitmq/amqp091-goSEMVER: introduced 0; fixed 1.13.01.13.0OSV record ↗aggregator derived · 1 Oct 2026
Gogithub.com/rabbitmq/amqp091-goSEMVER: introduced 0; fixed 1.13.01.13.0OSV record ↗aggregator derived · 1 Oct 2026
gogithub.com/rabbitmq/amqp091-go< 1.13.01.13.0GitHub advisory ↗upstream repository advisory · 17 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-77407 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/rabbitmq/amqp091-go: RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Fields
10 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • cryostat/cryostat-storage-rhel9 as a component of Cryostat 4
  • custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator as a component of Custom Metric Autoscaler operator for Red Hat Openshift
  • multicluster-globalhub/multicluster-globalhub-grafana-rhel9 as a component of Multicluster Global Hub
  • openshift-serverless-1/kn-plugin-event-sender-rhel9 as a component of OpenShift Serverless
  • rhacm2/acm-grafana-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
  • rhacm2/volsync-operator-bundle as a component of Red Hat Advanced Cluster Management for Kubernetes 2
  • rhacm2/volsync-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
  • rhoso-operators/rabbitmq-cluster-rhel9-operator as a component of Red Hat OpenStack Platform 18.0
  • quay/clair-rhel8 as a component of Red Hat Quay 3
  • quay/clair-rhel9 as a component of Red Hat Quay 3
Summary
A flaw was found in RabbitMQ amqp091-go, a Go client for AMQP 0.9.1. This vulnerability allows plaintext credentials to be exposed. After a successful PLAIN authentication handshake, the client retains passwords in an unencrypted format within its connection configuration. Local code with access to the connection object, such as logging or debugging tools, can access these sensitive credentials, leading to information disclosure. The credentials remain exposed for the entire duration of the connection.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-80805

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.0 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product stores sensitive information in cleartext in memory.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product stores sensitive information in cleartext in memory.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Cleartext Storage of Sensitive Information in Memory → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-316 ↗

CWE-316: Cleartext Storage of Sensitive Information in Memory. The product stores sensitive information in cleartext in memory.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:L

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SILowSubsequent-system integrity: A successful attack can cause a limited loss.SALowSubsequent-system availability: A successful attack can cause a limited loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
CWE-316
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-80805Official EUVD mapping

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.

Official EUVD record ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260923Security Bulletin 23 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Sep 2026, published on 23 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 16 Sept 2026 · Last source change 16 Sept 2026, 14:59 UTC · CWE-316 · Cleartext Storage of Sensitive Information in Memory

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-17
European sourceENISA EUVD · EUVD-2026-80805
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-77407 to remediation: access.redhat.com/CVE-2026-77407.
    Before
    remediation: access.redhat.com/CVE-2026-77407
    After
    remediation: access.redhat.com/CVE-2026-77407
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    cryostat/cryostat-storage-rhel9 as a component of Cryostat 4; custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator as a component of Custom Metric Autoscaler operator for Red Hat Openshift; multicluster-globalhub/multicluster-globalhub-grafana-rhel9 as a component of Multicluster Global Hub; openshift-serverless-1/kn-plugin-event-sender-rhel9 as a component of OpenShift Serverless; rhacm2/acm-grafana-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-operator-bundle as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhoso-operators/rabbitmq-cluster-rhel9-operator as a component of Red Hat OpenStack Platform 18.0; quay/clair-rhel8 as a component of Red Hat Quay 3; quay/clair-rhel9 as a component of Red Hat Quay 3
    After
    cryostat/cryostat-storage-rhel9 as a component of Cryostat 4; custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator as a component of Custom Metric Autoscaler operator for Red Hat Openshift; multicluster-globalhub/multicluster-globalhub-grafana-rhel9 as a component of Multicluster Global Hub; openshift-serverless-1/kn-plugin-event-sender-rhel9 as a component of OpenShift Serverless; rhacm2/acm-grafana-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-operator-bundle as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhoso-operators/rabbitmq-cluster-rhel9-operator as a component of Red Hat OpenStack Platform 18.0; quay/clair-rhel8 as a component of Red Hat Quay 3; quay/clair-rhel9 as a component of Red Hat Quay 3 · Fixed: opentelemetry-collector-contrib-0:0.161.0-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; opentelemetry-collector-contrib-0:0.161.0-0.1.hum1@src as a component of Red Hat Hardened Images; opentelemetry-collector-contrib-0:0.161.0-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  4. ENISA EUVD mappingEUVD-2026-80805 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-80805"}
    ENISA EUVD ↗
  5. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-80805↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-27GV-RFVV-22MV↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-77407 · cve.blacktree.nl