CVE-2026-49252: deepstreamIO deepstream.io · Prototype Pollution
Affects deepstreamIO deepstream.ioSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical : upgrade to 10.0.5 as a priority.
Data as of 31 Oct 2026, 08:20 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.0.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade deepstream.io and deepstreamio/deepstream.io to 10.0.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| deepstreamIOdeepstream.io | Affected
| Fixed in
|
GitHubdeepstreamio/deepstream.iopkg:github/deepstreamio/deepstream.ioOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in deepstream.io version 10.0.5. Users should upgrade to version 10.0.5 or later to remediate this vulnerability. No additional mitigation guidance is provided or required beyond applying the official fix.
Description
deepstream is a server that allows clients and backend services to sync data, send messages and make rpcs at scale. Versions prior to 10.0.5 are vulnerable to Prototype Pollution. Exploitation can lead to potential privilege escalation from any authenticated user with write permission to any record. This issue has been fixed in version 10.0.5.