chore(deps): update dependency python-socketio to v5.14.0 [security] #109
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==5.11.3->==5.14.0GitHub Vulnerability Alerts
CVE-2025-61765
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.
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
picklePython 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.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.
Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable.
Remediation
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
picklemodule and use the much safer JSON encoding for inter-server messaging.Release Notes
miguelgrinberg/python-socketio (python-socketio)
v5.14.0: Release 5.14.0Compare Source
See CHANGES.md for release notes.
v5.13.0: Release 5.13.0Compare Source
See CHANGES.md for release notes.
v5.12.1: Release 5.12.1Compare Source
See CHANGES.md for release notes.
v5.12.0: Release 5.12.0Compare Source
See CHANGES.md for release notes.
v5.11.4: Release 5.11.4Compare Source
See CHANGES.md for release notes.
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.