Skip to content

← Public intelligence

PyPI package

python-socketio

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5PyPIAmendedPublished

    python-socketio: Binary attachment accumulation can cause denial of service

    CVE-2026-48804 · GHSA-5w7q-77mv-v69f

    Affected
    • PyPI python-socketio <= 5.16.1
    Fixed in
    5.16.2· Vendor fix available
    Issue
    Impact The python-socketio server stores binary EVENT and ACK messages in memory while it waits to receive their binary attachments. Once all the attachments are received, these messages are then processed. An attacker can submit a binary message and intentionally omit sending one or more of its attachments to cause the message along with the partial list of received attachments to stay in memory for a long time. Patches Version 5.16.2 takes the following measures to address this issue: - Binary packets are only accepted from authenticated clients. - When a client disconnects, the server checks if there is a partial binary message being held for the client and deletes it.

    Recommended action: Upgrade to 5.16.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Medium, CVSS 6.4PyPIAmendedPublished

    python-socketio vulnerable to arbitrary Python code execution (RCE) through malicious pickle deserialization in certain multi-server deployments

    CVE-2025-61765 · GHSA-g8c6-8fjj-2r4m

    Affected
    • PyPI python-socketio >= 0.8.0, < 5.14.0
    Fixed in
    5.14.0· Vendor fix available
    Issue
    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 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. Impact This vulnerability only…

    Recommended action: Upgrade to 5.14.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →