CVE-2026-49998

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-16 20:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-24 20:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 8.2 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-07-16 20:16 UTC

Last modified

2026-10-24 20:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-347

Record status

Deferred

Attack profile CVSS 3.1 · 8.2

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-49998.md and follow it. Check whether this project is affected by CVE-2026-49998. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge