Bug 2535980

Summary: CVE-2026-77407 syncthing: RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Fields [epel-all]
Product: [Fedora] Fedora EPEL Reporter: Vipul Nair <vinair>
Component: syncthingAssignee: Fabio Valentini <decathorpe>
Status: ON_QA --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: epel10CC: decathorpe, go-sig, gwync, maxwell
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["b867578f-894a-47a2-a37f-a9631b49d974"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2535487    

Description Vipul Nair 2026-09-17 12:47:33 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Fedora Update System 2026-10-07 16:40:41 UTC
FEDORA-EPEL-2026-79e0927ac1 (syncthing-2.1.6-1.el10_4) has been submitted as an update to Fedora EPEL 10.4.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-79e0927ac1

Comment 2 Fedora Update System 2026-10-07 16:41:01 UTC
FEDORA-EPEL-2026-7addd7a2bf (syncthing-2.1.6-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7addd7a2bf

Comment 3 Fedora Update System 2026-10-07 16:41:19 UTC
FEDORA-EPEL-2026-05efddaadc (syncthing-2.1.6-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-05efddaadc

Comment 4 Fedora Update System 2026-10-08 01:24:49 UTC
FEDORA-EPEL-2026-05efddaadc has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-05efddaadc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-10-08 01:31:41 UTC
FEDORA-EPEL-2026-7addd7a2bf has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7addd7a2bf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-10-08 02:24:00 UTC
FEDORA-EPEL-2026-79e0927ac1 has been pushed to the Fedora EPEL 10.4 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-79e0927ac1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.