https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 15:01:19 +0000 https://vulnerability.circl.lu/vuln/cve-2025-61765 <p><strong>Affected:</strong> miguelgrinberg python-socketio</p> <p>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&#39;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&#39;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…</p> <p><strong>Affected:</strong> miguelgrinberg python-socketio</p> <p>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&#39;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&#39;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…</p> https://vulnerability.circl.lu/vuln/cve-2025-61765 https://vulnerability.circl.lu/vuln/ghsa-g8c6-8fjj-2r4m <p><strong>Affected:</strong> PyPI: python-socketio</p> <p>### Summary 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.</p> <p>### Details 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.</p> <p>The vulnerability stems from deserialization of messages using Python&#39;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&#39;s `__reduce__` method.</p> <p>### Impact 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.</p> <p>Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable.</p> <p>### Remediation In addition to making sure standard security practices are followed in the deployment of the message queue, users of the python-socketio package ca…</p> <p><strong>Affected:</strong> PyPI: python-socketio</p> <p>### Summary 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.</p> <p>### Details 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.</p> <p>The vulnerability stems from deserialization of messages using Python&#39;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&#39;s `__reduce__` method.</p> <p>### Impact 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.</p> <p>Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable.</p> <p>### Remediation In addition to making sure standard security practices are followed in the deployment of the message queue, users of the python-socketio package ca…</p> https://vulnerability.circl.lu/vuln/ghsa-g8c6-8fjj-2r4m https://vulnerability.circl.lu/vuln/pysec-2026-1854 <p><strong>Affected:</strong> PyPI: python-socketio</p> <p>### Summary 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.</p> <p>### Details 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.</p> <p>The vulnerability stems from deserialization of messages using Python&#39;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&#39;s `__reduce__` method.</p> <p>### Impact 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.</p> <p>Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable.</p> <p>### Remediation In addition to making sure standard security practices are followed in the deployment of the message queue, users of the python-socketio package ca…</p> <p><strong>Affected:</strong> PyPI: python-socketio</p> <p>### Summary 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.</p> <p>### Details 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.</p> <p>The vulnerability stems from deserialization of messages using Python&#39;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&#39;s `__reduce__` method.</p> <p>### Impact 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.</p> <p>Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable.</p> <p>### Remediation In addition to making sure standard security practices are followed in the deployment of the message queue, users of the python-socketio package ca…</p> https://vulnerability.circl.lu/vuln/pysec-2026-1854