`goreleaser release --debug` shows secretsGHSA-h3q2-8whx-c29h
MEDIUMFix: goreleaser/goreleaser@d5b6a53GHSA-h3q2-8whx-c29h is a medium-severity (CVSS 5.5) CWE-532 vulnerability in github.com/goreleaser/goreleaser. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/goreleaser/goreleaser — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-h3q2-8whx-c29h.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/goreleaser/goreleaserReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Hello 👋
goreleaser release --debug log shows secret values used in the in the custom publisher.
How to reproduce the issue:
- Define a custom publisher as the one below. Make sure to provide a custom script to the
cmdfield and to provide a secret toenv
#.goreleaser.yml
publishers:
- name: my-publisher
# IDs of the artifacts we want to sign
ids:
- linux_archives
- linux_package
cmd: "./build/package/linux_notarize.sh"
env:
- VERSION={{ .Version }}
- SECRET_1={{.Env.SECRET_1}}
- SECRET_2={{.Env.SECRET_2}}
- run
goreleaser release --debug
You should see your secret value in the gorelease log. The log shows also the GITHUB_TOKEN
Example:
running cmd= ....
SECRET_1=secret_value
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/goreleaser/goreleaser | ≥ 1.23.0&&< 1.24.0 | 1.24.0go get github.com/goreleaser/goreleaser@v1.24.0 |
Affected Products
goreleasergoreleaserResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goreleaser/goreleaser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/goreleaser/goreleaser to 1.24.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3q2-8whx-c29h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat rates this issue as having a Moderate impact since it requires a malicious user to have direct access to the GoReleaser commands by inserting the --debug flag and consuming the values from the logs. This normally requires an environment that is already compromised.
No mitigation is yet available for this vulnerability despite having control of the --debug and where the logs are located.Source: Red Hat security advisory for GHSA-h3q2-8whx-c29h (CC BY 4.0)
Frequently Asked Questions
Is GHSA-h3q2-8whx-c29h in your dependencies?
Find it across Go, including transitive dependencies.