https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 03 Nov 2026 20:53:12 +0000 https://db.gcve.eu/vuln/cve-2026-116685 <p><strong>Affected:</strong> modelcontextprotocol python-sdk</p> <p>The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.8.0 until 1.30.0 and 2.2.0, streamable_http_client, streamablehttp_client, sse_client, ClientSessionGroup, OAuth, and create_mcp_http_client client paths enable follow_redirects and follow redirects to a different origin, forwarding caller-supplied custom credential headers and, for 307 or 308 responses, the request body. An attacker who can influence a trusted endpoint&#39;s redirect destination can receive that material. This issue is fixed in versions 1.30.0 and 2.2.0.</p> <p><strong>Affected:</strong> modelcontextprotocol python-sdk</p> <p>The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.8.0 until 1.30.0 and 2.2.0, streamable_http_client, streamablehttp_client, sse_client, ClientSessionGroup, OAuth, and create_mcp_http_client client paths enable follow_redirects and follow redirects to a different origin, forwarding caller-supplied custom credential headers and, for 307 or 308 responses, the request body. An attacker who can influence a trusted endpoint&#39;s redirect destination can receive that material. This issue is fixed in versions 1.30.0 and 2.2.0.</p> https://db.gcve.eu/vuln/cve-2026-116685 https://db.gcve.eu/vuln/ghsa-5h93-6whr-6q8j <p><strong>Affected:</strong> PyPI: mcp</p> <p>### Summary In affected versions, the SDK&#39;s Streamable HTTP and SSE client transports followed HTTP redirects to any host. If the configured MCP endpoint answered with a redirect to a different origin:</p> <p>- custom headers set on the client (for example an `X-API-Key` credential) were sent to that origin, and - on a `307` or `308` redirect the request body was re-sent there too.</p> <p>The SDK&#39;s OAuth client providers followed redirects on their own discovery, registration and token requests in the same way.</p> <p>A lone `Authorization` bearer header was not exposed; the HTTP library already drops it on cross-origin redirects.</p> <p>Anyone able to make an endpoint you trust redirect elsewhere (a stale redirect to a lapsed domain, a misrouted proxy rule, redirect logic an attacker can influence) could capture that material. A server that is itself malicious gains nothing this way; it already receives your requests directly.</p> <p>### Am I affected? Yes, if your code uses the SDK as an MCP client over HTTP through any of:</p> <p>- `streamable_http_client` (on 2.x also `Client` given an `http://` or `https://` URL) - `streamablehttp_client` or `sse_client` - `ClientSessionGroup` with HTTP server parameters - the internal `create_mcp_http_client` helper</p> <p>This includes an HTTP client you passed in yourself with `follow_redirects=True`.</p> <p>Affected versions: 1.8.0 through 1.29.1, and 2.0.0 through 2.1.1.</p> <p>Not affected:</p> <p>- MCP servers - stdio clients - a client you supplied with `follow_redirects` left at its def…</p> <p><strong>Affected:</strong> PyPI: mcp</p> <p>### Summary In affected versions, the SDK&#39;s Streamable HTTP and SSE client transports followed HTTP redirects to any host. If the configured MCP endpoint answered with a redirect to a different origin:</p> <p>- custom headers set on the client (for example an `X-API-Key` credential) were sent to that origin, and - on a `307` or `308` redirect the request body was re-sent there too.</p> <p>The SDK&#39;s OAuth client providers followed redirects on their own discovery, registration and token requests in the same way.</p> <p>A lone `Authorization` bearer header was not exposed; the HTTP library already drops it on cross-origin redirects.</p> <p>Anyone able to make an endpoint you trust redirect elsewhere (a stale redirect to a lapsed domain, a misrouted proxy rule, redirect logic an attacker can influence) could capture that material. A server that is itself malicious gains nothing this way; it already receives your requests directly.</p> <p>### Am I affected? Yes, if your code uses the SDK as an MCP client over HTTP through any of:</p> <p>- `streamable_http_client` (on 2.x also `Client` given an `http://` or `https://` URL) - `streamablehttp_client` or `sse_client` - `ClientSessionGroup` with HTTP server parameters - the internal `create_mcp_http_client` helper</p> <p>This includes an HTTP client you passed in yourself with `follow_redirects=True`.</p> <p>Affected versions: 1.8.0 through 1.29.1, and 2.0.0 through 2.1.1.</p> <p>Not affected:</p> <p>- MCP servers - stdio clients - a client you supplied with `follow_redirects` left at its def…</p> https://db.gcve.eu/vuln/ghsa-5h93-6whr-6q8j