GitPython versions up to 3.1.50 contain a vulnerability where the Repo.clone_from() method expands environment variables in the remote URL via os.path.expandvars() before passing it to git clone. This allows an attacker controlling the URL argument to embed environment variable tokens that are expanded server-side, potentially exfiltrating secrets such as AWS keys or GitHub tokens. The vulnerability arises because polish_url() applies environment variable expansion indiscriminately to URLs without scheme checks or opt-outs. A fix is available in version 0.35.0_1.
The MCP Python SDK's experimental task handlers feature, when enabled, does not verify session ownership of tasks. This allows any connected client to list, read results from, and cancel tasks created by other clients on the same server. The vulnerability affects servers that enable the experimental tasks feature and use default handlers without session validation. It is fixed in version 1.27.2 and later, which embed session markers in task IDs and restrict task access to the owning session.
The MCP Python SDK's deprecated WebSocket server transport does not validate Host or Origin headers during the WebSocket handshake, allowing any web page to connect and issue JSON-RPC requests if the server is exposed without additional protections. This affects applications that explicitly use the deprecated websocket_server transport, which is not part of the MCP specification and must be manually integrated. The vulnerability can lead to unauthorized enumeration and invocation of server tools and resource access depending on the server's exposure. The issue is fixed in version 1.28.1 by adding optional Host and Origin validation, but upgrading alone does not enable validation unless configured. The recommended mitigation is to migrate away from the deprecated transport to Streamable HTTP, which enforces these protections automatically. The WebSocket transport is removed entirely in version 2.
A high-severity Denial of Service (DoS) vulnerability exists in Tornado's _parseparam function in httputil.py, affecting versions >=2.2.0 and <2.2.2_3. The function inefficiently parses multipart/form-data parameters, causing CPU usage to increase quadratically when processing crafted Content-Disposition headers. This can cause the Tornado server to become unresponsive due to its single event loop design.
The twisted.web HTTP server in Scrapy versions 2.9.0 up to but not including 2.11.2_3 can process HTTP pipelined requests out-of-order. This behavior may lead to information disclosure, especially when twisted.web servers are deployed behind reverse proxies with connection pooling. The issue has a high severity with a CVSS score of 8.3 and affects HTTP 1.0 and 1.1 pipelined requests.
CVE-2024-6345 is a high-severity vulnerability in the package_index module of pypa/setuptools up to version 69.1.1 that allows remote code execution via command injection through package URLs. The flaw arises from unsafe handling of download functions that process user-controlled or package index server URLs. This vulnerability is fixed in setuptools version 70.0.
Black, a code formatting tool, had a vulnerability where the cache file name was constructed using the unsanitized value of the --python-cell-magics option. This allowed an attacker controlling this option to write cache files to arbitrary file system locations. The issue is fixed in Black version 26.3.1.
A memory leak vulnerability exists in the UltraJSON (ujson) library versions 5.4.0 through 5.11.0 when parsing large integers outside the range [-2^63, 2^64 - 1]. This flaw can be triggered by any service using ujson to parse untrusted JSON inputs, potentially leading to denial of service (DoS). The leak involves accumulating copies of the string representation of large integers plus a null byte, regardless of whether parsing succeeds or fails. The issue is fixed in ujson version 5.12.0. No workarounds other than upgrading are available.
CVE-2026-32875 is a vulnerability in the UltraJSON (ujson) library used by python-lsp-server where integer overflow or underflow in handling the 'indent' parameter during JSON serialization can cause a segmentation fault (crash) or an infinite loop. This occurs when the product of the indent value and the nested depth exceeds the 32-bit integer limit or when a large negative indent is used. The issue can lead to denial of service. The vulnerability affects python-lsp-server versions >=1.6.0 and <1.14.0_1. A patch is available in ujson 5.12.0 that fixes the overflow and caps the indent value.
The joserfc Python JWT library has a vulnerability where logging error messages embeds non-decoded JWT token parts, allowing an attacker to cause uncontrolled resource consumption by sending arbitrarily large JWT bearer tokens. This can lead to excessively large log entries and memory usage during token decoding, especially if the web application is not protected by a production-grade web server or reverse proxy that enforces header size limits. The issue arises because the library raises an ExceededSizeError exception containing the full large payload, which is already loaded in memory. The vulnerability affects joserfc versions >=5.1.13 and <5.1.17 and is fixed in version 5.1.17.
The python-multipart library's parse_form() function did not validate the Content-Length header for negative values, causing it to read the entire request body into memory at once instead of in chunks. This vulnerability only affects code that directly calls parse_form() with attacker-controlled negative Content-Length headers without normalization. Common frameworks like Starlette and FastAPI are not affected. The impact is limited to potential memory exhaustion under concurrent requests in bespoke WSGI or http.server handlers. The issue is fixed in version 0.12.0_2, which rejects negative Content-Length values before reading the stream.