# CVE-2026-32301: Centrifugo: SSRF via unverified JWT claims interpolated into dynamic JWKS endpoint URL > An unauthenticated attacker can trigger SSRF in Centrifugo by crafting JWT claims that influence the dynamic JWKS endpoint URL before signature verification. - **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Mar 2026 - **Updated:** 13 Mar 2026 - **Also known as:** GHSA-j77h-rr39-c552, GO-2026-4702 ## What is CVE-2026-32301? CVE-2026-32301 is a critical server-side request forgery vulnerability in centrifugal centrifugo, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Centrifugo is an open-source scalable real-time messaging server. Prior to 6.7.0, Centrifugo is vulnerable to Server-Side Request Forgery (SSRF) when configured with a dynamic JWKS endpoint URL using template variables (e.g. {{tenant}}). An unauthenticated attacker can craft a JWT with a malicious iss or aud claim value that gets interpolated into the JWKS fetch URL before the token signature is verified, causing Centrifugo to make an outbound HTTP request to an attacker-controlled destination. This vulnerability is fixed in 6.7.0. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-32301? 15 open source packages ship an affected version, including github.com/centrifugal/centrifugo, github.com/centrifugal/centrifugo/v3 and github.com/centrifugal/centrifugo/v4. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/centrifugal/centrifugo` | Go | All versions | None | | `github.com/centrifugal/centrifugo` | Go | All versions to 2.4.0 | None | | `github.com/centrifugal/centrifugo` | Go | All versions to 2.4.0 | None | | `github.com/centrifugal/centrifugo/v3` | Go | All versions | None | | `github.com/centrifugal/centrifugo/v3` | Go | All versions to 3.2.3 | None | | `github.com/centrifugal/centrifugo/v3` | Go | All versions to 3.2.3 | None | | `github.com/centrifugal/centrifugo/v4` | Go | All versions | None | | `github.com/centrifugal/centrifugo/v4` | Go | All versions to 4.1.5 | None | | `github.com/centrifugal/centrifugo/v4` | Go | All versions to 4.1.5 | None | | `github.com/centrifugal/centrifugo/v5` | Go | All versions | None | | `github.com/centrifugal/centrifugo/v5` | Go | All versions to 5.4.9 | None | | `github.com/centrifugal/centrifugo/v5` | Go | All versions to 5.4.9 | None | | `github.com/centrifugal/centrifugo/v6` | Go | All versions | 6.7.0 | | `github.com/centrifugal/centrifugo/v6` | Go | All versions | 6.7.0 | | `github.com/centrifugal/centrifugo/v6` | Go | All versions | 6.7.0 | Products: Centrifugal Centrifugo. ## How do I fix CVE-2026-32301? Upgrade to a fixed version. ## Is CVE-2026-32301 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32301 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32301 and fix it if it is affected. What it is: CVE-2026-32301 is a critical server-side request forgery vulnerability in centrifugal centrifugo, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32301 exists. Affected packages and fixed versions: - github.com/centrifugal/centrifugo (Go): affected all versions; no fix listed - github.com/centrifugal/centrifugo (Go): affected all versions up to 2.4.0; no fix listed - github.com/centrifugal/centrifugo (Go): affected all versions up to 2.4.0; no fix listed - github.com/centrifugal/centrifugo/v3 (Go): affected all versions; no fix listed - github.com/centrifugal/centrifugo/v3 (Go): affected all versions up to 3.2.3; no fix listed - github.com/centrifugal/centrifugo/v3 (Go): affected all versions up to 3.2.3; no fix listed - github.com/centrifugal/centrifugo/v4 (Go): affected all versions; no fix listed - github.com/centrifugal/centrifugo/v4 (Go): affected all versions up to 4.1.5; no fix listed - github.com/centrifugal/centrifugo/v4 (Go): affected all versions up to 4.1.5; no fix listed - github.com/centrifugal/centrifugo/v5 (Go): affected all versions; no fix listed - github.com/centrifugal/centrifugo/v5 (Go): affected all versions up to 5.4.9; no fix listed - github.com/centrifugal/centrifugo/v5 (Go): affected all versions up to 5.4.9; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-32301/ (Markdown: https://insights.sbomify.com/CVE-2026-32301/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32301 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32301 - OSV: https://osv.dev/vulnerability/CVE-2026-32301 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32301/ Summaries are generated and may contain mistakes; the official description above is the record.