Secret disclosure via debug environment logging
Published Jan 30, 2024 · Updated May 29, 2025
Sensitive information exposure in GoReleaser 1.23.0 allows local users to read secrets from debug logs during custom publishing. The custom-publisher command path adds its entire environment array, including template-expanded secret values, to a debug log field. Exposure requires a release run with debug logging and configured publisher secrets, and can disclose those values and the GitHub token.
Summary
What happened
Sensitive information exposure in GoReleaser 1.23.0 allows local users to read secrets from debug logs during custom publishing. The custom-publisher command path adds its entire environment array, including template-expanded secret values, to a debug log field. Exposure requires a release run with debug logging and configured publisher secrets, and can disclose those values and the GitHub token.
The record
- CVE
- CVE-2024-23840
- Published
- Jan 30, 2024
- Updated
- May 29, 2025
- Vendor
- GoReleaser
- Product
- GoReleaser
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2024CVE publishedPublication date reported by the CVE source.
- May 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.23.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream debug-log secret exposure reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo