Code execution via untrusted pickle deserialization
Published Oct 6, 2025 · Updated Oct 6, 2025
Remote code execution in python-socketio before 5.14.0 allows attackers to run arbitrary Python code through crafted queue messages. A server-side message-queue manager passes received inter-server data directly to pickle.loads(), allowing a payload's reduce method to execute during deserialization. Exploitation requires prior access to the deployment's internal message queue; single-server deployments and multi-server deployments with a secure queue are not affected.
Summary
What happened
Remote code execution in python-socketio before 5.14.0 allows attackers to run arbitrary Python code through crafted queue messages. A server-side message-queue manager passes received inter-server data directly to pickle.loads(), allowing a payload's reduce method to execute during deserialization. Exploitation requires prior access to the deployment's internal message queue; single-server deployments and multi-server deployments with a secure queue are not affected.
The record
- CVE
- CVE-2025-61765
- Published
- Oct 6, 2025
- Updated
- Oct 6, 2025
- Vendor
- Miguel Grinberg
- Product
- python-socketio
- Classifications
- CWE-502, T1059.006
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2025CVE publishedPublication date reported by the CVE source.
- Oct 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.8.0, < 5.14.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo