Centrifugo is an open-source scalable real-time messaging server. Prior to 6.8.4, Centrifugo unidirectional WebSocket transport with uni_websocket.compression enabled enforced uni_websocket.message_size_limit against compressed wire-frame length in internal/websocket/conn.go advanceFrame, but ReadMessage used io.ReadAll after decompression without an output cap, allowing unauthenticated requests to /connection/uni_websocket to trigger large memory and CPU consumption. This issue is fixed in version 6.8.4.
CVE-2026-62963
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- —
- EPSS
- 22.3%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 17, 2026
Advisory Details (4)
Auto-updated Jul 16, 2026Decompression bomb DoS via permessage-deflate in unidirectional WebSocket transport · Advisory · centrifugal/centrifugo · GitHub
https://github.com/centrifugal/centrifugo/security/advisories/GHSA-q6mr-3g59-5m8xv6.8.4
Patch available: centrifugal/centrifugo v6.8.4
https://github.com/centrifugal/centrifugo/releases/tag/v6.8.4Bound default decompressed WebSocket message size, options to tweak the limit
Fix merged in centrifugal/centrifugo PR #1162 on 2026-06-28 — awaiting tagged release
https://github.com/centrifugal/centrifugo/pull/1162commit 46d40e4ac3a5 (centrifugal/centrifugo)
Fix landed in centrifugal/centrifugo commit 46d40e4ac3a5 — awaiting tagged release
https://github.com/centrifugal/centrifugo/commit/46d40e4ac3a5446c9745f8b219197166ae12a6e5Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:34 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 14:12 UTCEG score recompute
- 2026-07-16 19:45 UTCEG score recompute
- 2026-07-16 19:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-62963?
When was CVE-2026-62963 disclosed?
Is CVE-2026-62963 actively exploited?
What is the CVSS score of CVE-2026-62963?
How do I remediate CVE-2026-62963?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62963
Is Your Infrastructure Affected by CVE-2026-62963?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.