Vulnerability in @deepstream/server (CVE-2026-49252)
Summary
Vulnerability in @deepstream/server (CVE-2026-49252). Confidential information can be exposed externally. Exploitable via __proto__. Mitigation: upgrade to 10.0.5 or later.
Original description
The description as published by the source.
Impact
Prototype pollution in deepstream server v <=10.0.4. Potential privilege escalation from any authenticated user with write permission to any record.
Patches
Yes, upgrade to v10.0.5
Workarounds
Filter out all messages containing the path __proto__, constructor, prototype, before they reach the server's message pipeline
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49252 has been found in @deepstream/server.
Attackers can target a specific entry point like __proto__ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.9/10.
What to do: upgrade @deepstream/server to 10.0.5 or later.
If unsure, ask your IT team or search "@deepstream/server CVE-2026-49252" on the vendor's site.
CVE-2026-49252 (@deepstream/server) — CWE-1321 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: __proto__ / constructor / prototype
Patched: 10.0.5 — apply immediately
Workaround: Filter out all messages containing the path __proto__, constructor, prototype, before they reach the server's message pipeline
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in @deepstream/server. Attackers reach the vulnerable code path via __proto__.
Check the vendor advisory for the affected versions of @deepstream/server. Attack surface: __proto__ / constructor / prototype.
Severity: Critical (CVSS 9.9/10). Confidential information can be exposed externally.
Update to 10.0.5.
Workaround: Filter out all messages containing the path __proto__, constructor, prototype, before they reach the server's message pipeline
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@deepstream/server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@deepstream/server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@deepstream/serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Filter out all messages containing the path `__proto__`, `constructor`, `prototype`, **before they reach the server's message pipeline**パッチが適用されるまでの応急処置として、Filter out all messages containing the path
__proto__,constructor,prototype, before they reach the server's message pipeline を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade @deepstream/server to 10.0.5ステージング環境で 10.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com