What is GHSA-F6MM-5FC7-3G3C?

GHSA-F6MM-5FC7-3G3C is a medium-severity security vulnerability in github.com/goreleaser/goreleaser (go), affecting versions = 1.26.0. It is fixed in 1.26.1.

How severe is GHSA-F6MM-5FC7-3G3C?

GHSA-F6MM-5FC7-3G3C has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/goreleaser/goreleaser are affected by GHSA-F6MM-5FC7-3G3C?

github.com/goreleaser/goreleaser (go) versions = 1.26.0 is affected.

Is there a fix for GHSA-F6MM-5FC7-3G3C?

Yes. GHSA-F6MM-5FC7-3G3C is fixed in 1.26.1. Upgrade to this version or later.

Is GHSA-F6MM-5FC7-3G3C exploitable, and should I be worried?

Whether GHSA-F6MM-5FC7-3G3C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-F6MM-5FC7-3G3C is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-F6MM-5FC7-3G3C

Q: How do I fix GHSA-F6MM-5FC7-3G3C?

Upgrade github.com/goreleaser/goreleaser to 1.26.1 or later.

Summary

goreleaser shows environment by default

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.

GHSA-F6MM-5FC7-3G3C has a CVSS score of 6.2 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.26.1); upgrading removes the vulnerable code path.

Affected versions

github.com/goreleaser/goreleaser (= 1.26.0)

Security releases

github.com/goreleaser/goreleaser → 1.26.1 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/goreleaser/goreleaser to 1.26.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-F6MM-5FC7-3G3C? GHSA-F6MM-5FC7-3G3C is a medium-severity security vulnerability in github.com/goreleaser/goreleaser (go), affecting versions = 1.26.0. It is fixed in 1.26.1.
How severe is GHSA-F6MM-5FC7-3G3C? GHSA-F6MM-5FC7-3G3C has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/goreleaser/goreleaser are affected by GHSA-F6MM-5FC7-3G3C? github.com/goreleaser/goreleaser (go) versions = 1.26.0 is affected.
Is there a fix for GHSA-F6MM-5FC7-3G3C? Yes. GHSA-F6MM-5FC7-3G3C is fixed in 1.26.1. Upgrade to this version or later.
Is GHSA-F6MM-5FC7-3G3C exploitable, and should I be worried? Whether GHSA-F6MM-5FC7-3G3C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-F6MM-5FC7-3G3C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-F6MM-5FC7-3G3C? Upgrade github.com/goreleaser/goreleaser to 1.26.1 or later.