CVE-2026-49998Disclosure

LOWCVSS 8.2 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-347

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-07-01: 1Technical Details · 2026-07-01: 107-01
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
Full discourse1 post
  • DailyCVE@dailycve
    Disclosure

    🔴 Centrifugo, Cross-Tenant JWT Authentication Bypass via JWKS Cache Kid Collision, #CVE-2026-49998 (High) -DC-Jul2026-809 https://dailycve.com/centrifugo-cross-tenant-jwt-authentication-bypass-via-jwks-cache-kid-collision-cve-2026-49998-high-dc-jul2026-809/

    Post summary

    A high‑severity cross‑tenant JWT authentication bypass through a JWKS cache key‑ID collision (CVE‑2026‑49998) has been disclosed, but the post provides no proof‑of‑concept, exploit code, or evidence of active exploitation.

    0000046
    217 followersView on X

Explore more