cve.bz

CVE-2025-61765 miguelgrinberg python-socketio: Deserialization of Untrusted Data

6.4 mediumEPSS 0.5%Fix available

Medium (6.4) in miguelgrinberg python-socketio. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in python-socketio 5.14.0.

On this page
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.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-61765 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-61765?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-61765?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-61765 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
miguelgrinberg python-socketio>= 0.8.0, < 5.14.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g8c6-8fjj-2r4mPyPIpython-socketio>=0.8.0 <5.14.05.14.0
PYSEC-2026-1854PyPIpython-socketio>=0.8.0 <5.14.05.14.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-socketiono fix listedDEBIAN-CVE-2025-61765
Debian14python-socketio5.16.0-1DEBIAN-CVE-2025-61765
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 3 morepython-socketiono fix listedUBUNTU-CVE-2025-61765
SUSELinux Enterprise Module for Python 3 15 SP6, Linux Enterprise Module for Python 3 15 SP7python-python-socketio5.7.2-150600.3.3.1SUSE-SU-2025:3780-1
openSUSELeap 15.6python-python-socketio5.7.2-150600.3.3.1SUSE-SU-2025:3780-1
openSUSETumbleweedpython-python-socketio5.14.1-1.1openSUSE-SU-2025:15613-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • locus-x64/CVE-2025-61765_PoC Harbor Check: matches CVE 1 star, created
    Proof of Concept of an unsafe pickle deserialization vulnerability in Socket.IO

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON