GHSA-g8c6-8fjj-2r4m · Severity: medium · Ecosystem: pip — python-socketio vulnerable to arbitrary Python code execution (RCE) through malicious pickle deserialization in certain multi-server deployments
python-socketio is a Python implementation of the Socket.IO realtime client and server. A remote code execution vulnerability in python-socketio versions prior to 5.14.0 allows attackers to execute arbitrary Python code through malicious pickle deserialization in multi-server deployments on which the attacker previously gained access to the message queue that the servers use for internal communications. When Socket.IO servers are configured to use a message queue backend such as Redis for inter-server communication, messages sent between the servers are encoded using the `pickle` Python module. When a server receives one of these messages through the message queue, it assumes it is trusted and immediately deserializes it. The vulnerability stems from deserialization of messages using Python's `pickle.loads()` function. Having previously obtained access to the message queue, the attacker can send a python-socketio server a crafted pickle payload that executes arbitrary code during deserialization via Python's `__reduce__` method. This vulnerability only affects deployments with a compromised message queue. The attack can lead to the attacker executing random code in the context of, and with the privileges of a Socket.IO server process. Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable. In addition to making sure standard security practices are followed in the deployment of the message queue, users of the python-socketio package can upgrade to version 5.14.0 or newer, which remove the `pickle` module and use the much safer JSON encoding for inter-server messaging.
Conclusion & alert: CVE-2025-61765 is rated Low Risk (37.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.46%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2026-06-15 | 0.90% | 0.46% | -0.44% |
| 2 | 2026-06-11 | 0.84% | 0.90% | +0.06% |
| 3 | 2026-05-12 | — | 0.84% | — |
Full EPSS history (14 records total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 6.4 | 3.1 | MEDIUM |
|
0.9 | 5.5 | [email protected] |
GHSA-g8c6-8fjj-2r4m · Severity: medium · Ecosystem: pip — python-socketio vulnerable to arbitrary Python code execution (RCE) through malicious pickle deserialization in certain multi-server deployments
| vendor | priority | summary | link |
|---|---|---|---|
debian
|
not yet assigned | CVE-2025-61765 not yet assigned priority: Debian including 1 source packages (python-socketio), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. | https://security-tracker.debian.org/tracker/CVE-2025-61765 |
suse
|
medium | — | https://www.suse.com/security/cve/CVE-2025-61765/ |
ubuntu
|
medium | CVE-2025-61765 medium priority: Ubuntu including 1 source packages (python-socketio), 6 status rows across 6 suites (focal, jammy, noble, plucky, questing, upstream): needs-triage 5, ignored 1. | https://ubuntu.com/security/CVE-2025-61765 |
| Vendor | Product | Version | Raw CPE |
|---|---|---|---|
| No affected products in dataset. | |||