GHSA-f6mm-5fc7-3g3c is a medium-severity (CVSS 6.2) vulnerability in github.com/goreleaser/goreleaser. A fix is available for github.com/goreleaser/goreleaser — see the affected versions and patch details below.
goreleaser shows environment by default
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
Since #4787 the log output is printed on the INFO level, while previously it was logged on DEBUG. This means if the go build output is non-empty, goreleaser leaks the environment.
PoC
- Create a Go project with dependencies, do not pull them yet (or run goreleaser later in a container, or delete
$GOPATH/pkg). - Make sure to have secrets set in the environment
- Make sure to not have
go mod tidyin a before hook - Run
goreleaser release --clean - Go prints lots of
go: downloading ...lines, which triggers the "if output not empty, log it" line, which includes the environment.
Impact
Credentials and tokens are leaked.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/goreleaser/goreleaser | ≥ 1.26.0&&< 1.26.1 | 1.26.1go get github.com/goreleaser/goreleaser@v1.26.1 |
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.26.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6mm-5fc7-3g3c 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f6mm-5fc7-3g3c can be triaged on real exposure rather than presence alone.
Tailored to GHSA-f6mm-5fc7-3g3c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f6mm-5fc7-3g3c in your dependencies?
O3 Security finds GHSA-f6mm-5fc7-3g3c across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.