CVE-2026-49998
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.
What this means
- Exposure
- Exploitable remotely over the network, with an ordinary user account and with no action from the victim. The attack does require particular conditions, which makes it less systematic.
- Impact
- An attacker can read sensitive data and modify or destroy data. The impact spreads beyond the vulnerable component into other parts of the system.
- Weakness
- A cryptographic signature is not properly verified, so forged content passes as authentic.
- Likelihood
- Its EPSS score stays low: nothing points to imminent exploitation, which is no reason to leave it unpatched.
What to doFold into the next patch cycle.
Read automatically from the CVSS vector, the weakness type (CWE) and the EPSS score. The technical description above remains the one published by NIST.