CVE-2026-49998: CWE-347: Improper Verification of Cryptographic Signature in centrifugal centrifugo
Centrifugo, an open-source real-time messaging server, had a vulnerability prior to version 6.8.1 where its dynamic JWKS endpoint verification could incorrectly reuse a cryptographic key across different allowed issuers. This was due to caching and lookup mechanisms keyed only by the JWT header kid, ignoring other critical factors such as the resolved JWKS endpoint, issuer, audience, or trust-domain namespace. The issue 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 before version 6.8.1. The dynamic JWKS endpoint verification reused keys for one allowed issuer to verify JWTs for another allowed issuer because the JWKS cache and singleflight lookup keyed only by the JWT header kid. This flaw affected components including client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, internal/jwks/cache.go, and internal/jwks/manager.go. The vulnerability could allow an attacker to bypass issuer validation, potentially leading to privilege escalation or unauthorized access. The issue is resolved in Centrifugo version 6.8.1.
Potential Impact
The vulnerability allows improper verification of JWT signatures by reusing keys across different allowed issuers, which can lead to compromise of authentication and authorization mechanisms. This can result in an attacker forging tokens that are accepted as valid for different issuers, causing a high impact on confidentiality and integrity. Availability is not affected.
Mitigation Recommendations
Upgrade Centrifugo to version 6.8.1 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory stating the issue is resolved in 6.8.1. No other mitigation is indicated or required.
CVE-2026-49998: CWE-347: Improper Verification of Cryptographic Signature in centrifugal centrifugo
Description
Centrifugo, an open-source real-time messaging server, had a vulnerability prior to version 6.8.1 where its dynamic JWKS endpoint verification could incorrectly reuse a cryptographic key across different allowed issuers. This was due to caching and lookup mechanisms keyed only by the JWT header kid, ignoring other critical factors such as the resolved JWKS endpoint, issuer, audience, or trust-domain namespace. The issue 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 before version 6.8.1. The dynamic JWKS endpoint verification reused keys for one allowed issuer to verify JWTs for another allowed issuer because the JWKS cache and singleflight lookup keyed only by the JWT header kid. This flaw affected components including client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, internal/jwks/cache.go, and internal/jwks/manager.go. The vulnerability could allow an attacker to bypass issuer validation, potentially leading to privilege escalation or unauthorized access. The issue is resolved in Centrifugo version 6.8.1.
Potential Impact
The vulnerability allows improper verification of JWT signatures by reusing keys across different allowed issuers, which can lead to compromise of authentication and authorization mechanisms. This can result in an attacker forging tokens that are accepted as valid for different issuers, causing a high impact on confidentiality and integrity. Availability is not affected.
Mitigation Recommendations
Upgrade Centrifugo to version 6.8.1 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory stating the issue is resolved in 6.8.1. No other mitigation is indicated or required.
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/16/2026, 20:02:46 UTC
Last updated: 07/16/2026, 20:07:29 UTC
Views: 2
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.