← Back
CVE-2025-61765
Unsafe Deserialization in python-socketio (CVE-2025-61765)
Summary
vulnerability in python-socketio (CVE-2025-61765). Confidential information can be exposed externally. Exploitable via ``pickle``. Mitigation: upgrade to `5.14.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-61765** has been found in python-socketio.
Attackers can target a specific entry point like ``pickle`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade python-socketio to **5.14.0** or later.
If unsure, ask your IT team or search "python-socketio CVE-2025-61765" on the vendor's site.
CVE-2025-61765 (python-socketio) — CWE-502 /
Attack vector: adjacent-network / no user interaction
Attack surface: `pickle` / `__reduce__`
Patched: `5.14.0` — apply immediately
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.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in python-socketio. Attackers reach the vulnerable code path via ``pickle`` without authentication.
📍 Affected scope
python-socketio — . Attack surface: `pickle` / `__reduce__`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **5.14.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'python-socketio' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'python-socketio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `python-socketio` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade python-socketio to 5.14.0ステージング環境で 5.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
python-socketio
[{"type":"ECOSYSTEM","events":[{"introduced":"0.8.0"},{"fixed":"5.14.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-61765
- advisory https://github.com/advisories/GHSA-g8c6-8fjj-2r4m
- package https://github.com/miguelgrinberg/python-socketio
- package https://pypi.org/project/python-socketio
- web https://github.com/miguelgrinberg/python-socketio/security/advisories/GHSA-g8c6-8fjj-2r4m
- web https://github.com/miguelgrinberg/python-socketio/commit/53f6be094257ed81476b0e212c8cddd6d06ca39a
- web https://www.bluerock.io/post/cve-2025-61765-bluerock-discovers-critical-rce-in-socket-io-ecosystem