Server-side Request Forgery (SSRF) Affecting github.com/centrifugal/centrifugo/v4/internal/apiproto package, versions <6.7.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-GITHUBCOMCENTRIFUGALCENTRIFUGOV4INTERNALAPIPROTO-15666781
- published16 Mar 2026
- disclosed13 Mar 2026
- creditVarshank Naik
Introduced: 13 Mar 2026
CVE-2026-32301 Â (opens in a new tab)How to fix?
Upgrade github.com/centrifugal/centrifugo/v4/internal/apiproto to version 6.7.0 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the fetchKey function. An attacker can cause the server to make arbitrary HTTP requests to attacker-controlled destinations by crafting a JWT with malicious claim values that are interpolated into the JWKS endpoint URL before signature verification. This can allow access to internal network resources or enable authentication bypass by serving a malicious JWKS response.
Note: This is only exploitable if the configuration uses a dynamic JWKS endpoint URL with template variables combined with issuer or audience regular expressions.
Workaround
This vulnerability can be mitigated by restricting template variables in the JWKS endpoint URL to only the kid header field, rather than allowing arbitrary claim values.