Skip to main content
VulnerabilityPublished

CVE-2026-63116: deepstreamIO deepstream.io · Missing Authorization

Affects deepstreamIO deepstream.ioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 10.1.1 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.1.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade deepstream.io and deepstreamio/deepstream.io to 10.1.1.

Affected software

ProductAffectedFixed in
deepstreamIOdeepstream.ioAffected
  • >=10.1.0 <10.1.1
Fixed in
  • 10.1.1
GitHubdeepstreamio/deepstream.iopkg:github/deepstreamio/deepstream.ioOther threatsAffected
  • >=10.1.0 <10.1.1
Fixed in
  • 10.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade deepstream.io to version 10.1.1 or later, where this authorization issue is fixed. No other mitigations are indicated by the vendor advisory.

Description

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.

References

Community reviews

Loading reviews…