Server-Side Request Forgery (SSRF) Affecting goreleaser package, versions <2.15.4-r2


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-WOLFILATEST-GORELEASER-16630791
  • published11 May 2026
  • disclosed14 May 2026

Introduced: 11 May 2026

NewCVE-2026-44428  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Wolfi goreleaser to version 2.15.4-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream goreleaser package and not the goreleaser package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

The MCP Registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. Prior to 1.7.6, the client-side and server-side GitHub OIDC flow is bound only to a global audience string, not to the specific registry instance being targeted. On the client side, the publisher always appends audience=mcp-registry when requesting the GitHub Actions ID token, regardless of the selected --registry URL. On the server side, the exchange endpoint validates only that same fixed audience and then derives publish permissions directly from repository_owner. As a result, a token legitimately obtained while interacting with one registry deployment remains acceptable to any other deployment that shares the same code and audience string. This vulnerability is fixed in 1.7.6.

CVSS Base Scores

version 3.1