Vulnerability in github.com/centrifugal/centrifugo/v6 (CVE-2026-49998)
Summary
Vulnerability in github.com/centrifugal/centrifugo/v6 (CVE-2026-49998). Confidential information can be exposed externally. Exploitable via singleflight. Mitigation: upgrade to 6.8.1 or later.
Original description
The description as published by the source.
Centrifugo is an open-source scalable real-time messaging server. Prior to 6.8.1, Centrifugo dynamic JWKS endpoint verification could reuse a key for one allowed issuer to verify a JWT for another allowed issuer because the JWKS cache and singleflight lookup were keyed only by JWT header kid, not by the resolved JWKS endpoint, issuer, audience, or trust-domain namespace, affecting client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, internal/jwks/cache.go, and internal/jwks/manager.go. This issue is fixed in version 6.8.1.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49998 has been found in github.com/centrifugal/centrifugo/v6.
Attackers can target a specific entry point like singleflight over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade github.com/centrifugal/centrifugo/v6 to 6.8.1 or later.
If unsure, ask your IT team or search "github.com/centrifugal/centrifugo/v6 CVE-2026-49998" on the vendor's site.
CVE-2026-49998 (github.com/centrifugal/centrifugo/v6) — CWE-347 / CVSS v3 8.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: singleflight / kid / iss / aud
Patched: 6.8.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in github.com/centrifugal/centrifugo/v6. Attackers reach the vulnerable code path via singleflight.
Check the vendor advisory for the affected versions of github.com/centrifugal/centrifugo/v6. Attack surface: singleflight / kid / iss / aud.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 6.8.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/centrifugal/centrifugo/v6' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/centrifugal/centrifugo/v6' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/centrifugal/centrifugo/v6を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/centrifugal/centrifugo/v6 to 6.8.1ステージング環境で 6.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com