deepstream is a server that allows clients and backend services to sync data, send messages and make rpcs at scale. From 10.1.0 until 10.1.1, src/services/permission/valve/rules-map.ts omits RECORD_ACTION.PATCH_MULTI from RULES_MAP. When an authenticated user sends a PATCH_MULTI record operation while permission.type is config, getRulesForMessage returns a null rule specification and ConfigPermission.canPerformAction treats the missing specification as an unconditional allow instead of applying RULE_TYPES.WRITE. Any authenticated user can therefore modify arbitrary protected records, corrupt application state, or cause service disruption; deployments using the default permission type none already allow all operations and are not additionally affected. This issue is fixed in version 10.1.1.
CVE-2026-63116
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% 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.8
- EG Score
- 8.8(medium)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity88% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
September 21, 2026
Last Modified
September 24, 2026
Advisory Details (3)
Auto-updated Sep 21, 2026Release v10.1.1
Patch available: deepstreamIO/deepstream.io v10.1.1
https://github.com/deepstreamIO/deepstream.io/releases/tag/v10.1.1commit 1c2adde6581c (deepstreamIO/deepstream.io)
Fix landed in deepstreamIO/deepstream.io commit 1c2adde6581c — awaiting tagged release
https://github.com/deepstreamIO/deepstream.io/commit/1c2adde6581c53ef47e204364bc740bc3c2e2e2aPATCH_MULTI action bypasses Valve permission system allowing unauthorized record writes · Advisory · deepstreamIO/deepstream.io · GitHub
https://github.com/deepstreamIO/deepstream.io/security/advisories/GHSA-89vx-jh4q-vg3wVendor Advisories for CVE-2026-63116(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @deepstream/server | 10.1.0 | 10.1.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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-09-24 16:10 UTCEG score recompute
- 2026-09-24 04:34 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 17:41 UTCEG score recompute
- 2026-09-21 17:25 UTCEG score recompute
- 2026-09-21 17:10 UTCEG score recompute
- 2026-09-21 17:10 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-63116?
When was CVE-2026-63116 disclosed?
Is CVE-2026-63116 actively exploited?
What is the CVSS score of CVE-2026-63116?
How do I remediate CVE-2026-63116?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63116
Is Your Infrastructure Affected by CVE-2026-63116?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.