6.4

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

CVSS: 6.4v3.1MediumDeferred
AliasesSUSE-SU-2025:3780-1GHSA-g8c6-8fjj-2r4mPYSEC-2026-1854
Published 06-10-2025Last modified 22-10-2025

Vulnerability summary

CVE-2025-61765 is a medium (CVSS 6.4) Deserialization of Untrusted Data vulnerability in miguelgrinberg python-socketio. EPSS estimates a 0.48% chance of exploitation in the next 30 days, higher than 40.1% of scored vulnerabilities.

Overall risk
26/100
0100
Medium · default modelHow is this calculated?
CVSS score
6.4/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.48%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 0 · Related 3

Timeline

  1. 06-10-2025
    PublishedVulnerability first disclosed.
  2. 22-10-2025
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

7 scores · 7 sources · 1 version

EPSS trend

Probability

0.48%

Chance of exploitation in the next 30 days

Percentile

40%

Versus all other CVEs

30-day change

0.00 pp

From 0.48% on 18-09-2026

18-09-202618-10-2026
EPSS score
0.48%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard3 products
  • open-webui< 0.6.33-r1
  • open-webui-compat< 0.6.33-r1
  • reflex< 0.8.14-r0
Wolfi3 products
  • open-webui< 0.6.33-r1
  • open-webui-compat< 0.6.33-r1
  • reflex< 0.8.14-r0
Opensuse2 products
  • python-python-socketio&distro=openSUSE Leap 15.6< 5.7.2-150600.3.3.1
  • python-python-socketio&distro=openSUSE Tumbleweed< 5.14.1-1.1
Suse2 products
  • python-python-socketio&distro=SUSE Linux Enterprise Module for Python 3 15 SP6< 5.7.2-150600.3.3.1
  • python-python-socketio&distro=SUSE Linux Enterprise Module for Python 3 15 SP7< 5.7.2-150600.3.3.1
Debian1 product
  • python-socketioAll versions (No fix recorded) | < 5.16.0-1
Miguelgrinberg1 product
PyPI1 product
  • python-socketio≥ 0.8.0, < 5.14.0
Ubuntu1 product
  • python-socketioAll versions (No fix recorded)

8 vendors · 14 products

References

14 links
Show all 14 references