Vulnerability in socket.io-parser (CVE-2026-69185)
Summary
Vulnerability in socket.io-parser (CVE-2026-69185). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.3.6 or later.
Original description
The description as published by the source.
Impact
A specially crafted Socket.IO packet can make the server wait for a large number of binary attachments and buffer them, which can be exploited to make the server run out of memory.
Patches
| Version range | Used by | Fixed version |
|---|---|---|
>=4.0.0 <4.2.7 |
socket.io@4.x and socket.io-client@4.x |
4.2.7 |
>=3.4.0 <3.4.5 |
socket.io@2.x |
3.4.5 |
<3.3.6 |
socket.io-client@2.x |
3.3.6 |
Workarounds
There is no known workaround except upgrading to a safe version.
For more information
If you have any questions or comments about this advisory:
- Open a discussion here
Source: GitHub Security Advisories (Global) 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-69185 has been found in socket.io-parser.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade socket.io-parser to 3.3.6 or later.
If unsure, ask your IT team or search "socket.io-parser CVE-2026-69185" on the vendor's site.
CVE-2026-69185 (socket.io-parser) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.3.6 — apply immediately
Workaround: There is no known workaround except upgrading to a safe version.
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-20) exists in socket.io-parser.
Check the vendor advisory for the affected versions of socket.io-parser.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 3.3.6.
Workaround: There is no known workaround except upgrading to a safe version.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'socket.io-parser' . 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 'socket.io-parser' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
socket.io-parserを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There is no known workaround except upgrading to a safe version.パッチが適用されるまでの応急処置として、There is no known workaround except upgrading to a safe version. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade socket.io-parser to 3.3.6ステージング環境で 3.3.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-69185 node-socket.io-parser
- Ubuntu UBUNTU-CVE-2026-69185 node-socket.io-parser