Vulnerability Description
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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/centrifugal/centrifugo/commit/15d785015c6f318c1b68ea40b813699
- https://github.com/centrifugal/centrifugo/pull/1142
- https://github.com/centrifugal/centrifugo/releases/tag/v6.8.1
- https://github.com/centrifugal/centrifugo/security/advisories/GHSA-g6vg-wj8f-48c
- https://github.com/centrifugal/centrifugo/security/advisories/GHSA-g6vg-wj8f-48c
FAQ
What is CVE-2026-49998?
CVE-2026-49998 is a vulnerability with a CVSS score of 8.2 (HIGH). 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 all...
How severe is CVE-2026-49998?
CVE-2026-49998 has been rated HIGH with a CVSS base score of 8.2/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-49998?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.