goreleaser shows environment by default
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-532.
Summary
### 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 tidy` in 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/goreleaser/goreleaser (Go) | 1.26.0 to before 1.26.1 | 1.26.1 | Patch available | GHSA-f6mm-5fc7-3g3c |
- github.com/goreleaser/goreleaser (Go) Vendor— Affected 1.26.0 to before 1.26.1 Fixed in 1.26.1 Patch available GHSA-f6mm-5fc7-3g3c
Remediation
- Fix · GHSA-f6mm-5fc7-3g3c github.com/goreleaser/goreleaser (Go) Fixed in 1.26.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-f6mm-5fc7-3g3c
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences