Server-side Request Forgery (SSRF) Affecting github.com/distribution/distribution/v3/registry/proxy package, versions <3.1.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 IDSNYK-GOLANG-GITHUBCOMDISTRIBUTIONDISTRIBUTIONV3REGISTRYPROXY-15922299
- published7 Apr 2026
- disclosed6 Apr 2026
- creditOleh Konko
Introduced: 6 Apr 2026
CVE-2026-33540 Â (opens in a new tab)How to fix?
Upgrade github.com/distribution/distribution/v3/registry/proxy to version 3.1.0 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the process that parses WWW-Authenticate challenges from an upstream registry. An attacker can obtain upstream credentials by manipulating the bearer realm URL to redirect authentication requests to an attacker-controlled endpoint.