CVE-2026-49998

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
53(Track*)
EG Risk 53/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
18.3%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 17, 2026

Advisory Details (4)

Auto-updated Jul 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Dynamic JWKS key cache keyed only by `kid` allows cross-issuer JWT authentication bypass · Advisory · centrifugal/centrifugo · GitHub

https://github.com/centrifugal/centrifugo/security/advisories/GHSA-g6vg-wj8f-48cj
github_release Patch Available

v6.8.1

Patch available: centrifugal/centrifugo v6.8.1

https://github.com/centrifugal/centrifugo/releases/tag/v6.8.1
github_pr

Fix: Scope JWKS cache by resolved endpoint URL

Fix merged in centrifugal/centrifugo PR #1142 on 2026-05-27 — awaiting tagged release

https://github.com/centrifugal/centrifugo/pull/1142
github_commit

commit 15d785015c6f (centrifugal/centrifugo)

Fix landed in centrifugal/centrifugo commit 15d785015c6f — awaiting tagged release

https://github.com/centrifugal/centrifugo/commit/15d785015c6f318c1b68ea40b813699c9f8bd2c4

Vendor Advisories for CVE-2026-49998(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 1 ecosystem)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:18 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 03:52 UTCEG score recompute
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-17 15:35 UTCEG score recompute
  12. 2026-07-01 21:02 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49998?
CVE-2026-49998 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-49998 disclosed?
CVE-2026-49998 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49998 actively exploited?
CVE-2026-49998 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49998?
CVE-2026-49998 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-49998?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49998, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49998

Explore →

Is Your Infrastructure Affected by CVE-2026-49998?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.