CVE-2026-49998: CWE-347: Improper Verification of Cryptographic Signature in centrifugal centrifugo
Centrifugo versions prior to 6.8.1 contain a vulnerability in the dynamic JWKS endpoint verification process. The issue arises because the JWKS cache and singleflight lookup use only the JWT header 'kid' as a key, ignoring other important factors such as the resolved JWKS endpoint, issuer, audience, or trust-domain namespace. This flaw allows a key intended for one allowed issuer to be reused to verify a JWT from a different allowed issuer. The vulnerability is fixed in version 6.8.1.
AI Analysis
Technical Summary
CVE-2026-49998 is an improper verification of cryptographic signature vulnerability (CWE-347) in Centrifugo, an open-source real-time messaging server. Before version 6.8.1, the dynamic JWKS endpoint verification mechanism keyed its JWKS cache and singleflight lookup solely by the JWT header 'kid'. This insufficient keying allows reuse of a cryptographic key across different allowed issuers, potentially enabling an attacker to forge or misuse JWTs by exploiting the shared key cache. The affected components include client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, and internal JWKS cache and manager modules. The issue is resolved in Centrifugo 6.8.1.
Potential Impact
This vulnerability can lead to a high-impact compromise of JWT validation, allowing an attacker to bypass issuer verification and potentially impersonate other allowed issuers. This breaks the trust model of JWT authentication, resulting in confidentiality and integrity violations of the authentication tokens. The CVSS score of 8.2 reflects a high severity with network attack vector, high complexity, low privileges required, no user interaction, and complete confidentiality and integrity impact.
Mitigation Recommendations
Upgrade Centrifugo to version 6.8.1 or later, where this vulnerability is fixed. There is no indication of alternative mitigations or temporary workarounds. Patch status is confirmed by the vendor stating the fix is included in version 6.8.1.
CVE-2026-49998: CWE-347: Improper Verification of Cryptographic Signature in centrifugal centrifugo
Description
Centrifugo versions prior to 6.8.1 contain a vulnerability in the dynamic JWKS endpoint verification process. The issue arises because the JWKS cache and singleflight lookup use only the JWT header 'kid' as a key, ignoring other important factors such as the resolved JWKS endpoint, issuer, audience, or trust-domain namespace. This flaw allows a key intended for one allowed issuer to be reused to verify a JWT from a different allowed issuer. The vulnerability is fixed in version 6.8.1.
CVSS v3.1
Score 8.2high
Affected software
pkg:github/centrifugal/centrifugoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-49998 is an improper verification of cryptographic signature vulnerability (CWE-347) in Centrifugo, an open-source real-time messaging server. Before version 6.8.1, the dynamic JWKS endpoint verification mechanism keyed its JWKS cache and singleflight lookup solely by the JWT header 'kid'. This insufficient keying allows reuse of a cryptographic key across different allowed issuers, potentially enabling an attacker to forge or misuse JWTs by exploiting the shared key cache. The affected components include client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, and internal JWKS cache and manager modules. The issue is resolved in Centrifugo 6.8.1.
Potential Impact
This vulnerability can lead to a high-impact compromise of JWT validation, allowing an attacker to bypass issuer verification and potentially impersonate other allowed issuers. This breaks the trust model of JWT authentication, resulting in confidentiality and integrity violations of the authentication tokens. The CVSS score of 8.2 reflects a high severity with network attack vector, high complexity, low privileges required, no user interaction, and complete confidentiality and integrity impact.
Mitigation Recommendations
Upgrade Centrifugo to version 6.8.1 or later, where this vulnerability is fixed. There is no indication of alternative mitigations or temporary workarounds. Patch status is confirmed by the vendor stating the fix is included in version 6.8.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-02T18:30:51.283Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59358268715ace439a6865
Added to database: 07/16/2026, 19:48:18 UTC
Last enriched: 07/23/2026, 22:50:05 UTC
Last updated: 08/29/2026, 22:52:12 UTC
Views: 67
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.