Skip to content

docs: Add product-updates entry for Serverless SDK SSRF download hardening (1.11.1) #759

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
promptless wants to merge 1 commit into from
Closed

docs: Add product-updates entry for Serverless SDK SSRF download hardening (1.11.1) #759

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions release-notes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,10 @@ rss: true

<Accordion title="July 2026" defaultOpen>

**July 28, 2026**

<h4><Badge color="red">Security</Badge> Serverless Python SDK blocks SSRF in file downloads</h4> The Serverless Python SDK now refuses job-input download URLs that resolve to non-public addresses, including the cloud instance-metadata endpoint (169.254.169.254), loopback, and private RFC 1918 ranges. It allows only `http` and `https` URLs, re-validates every redirect, and caps download size. This ships in the `runpod` Python SDK 1.11.1. Set `RUNPOD_ALLOW_PRIVATE_DOWNLOAD_URLS` (opt-in, default off) to re-allow downloads from private or same-VPC addresses when you need them. Use `RUNPOD_MAX_DOWNLOAD_BYTES` to change the per-download cap (default 5 GiB).

**July 23, 2026**

<h4><Badge color="green">New Release</Badge> [Runpod API v2 (BETA)](/api-reference-v2/overview) </h4> A new REST API is available in public beta. See the [API v2 reference](/api-reference-v2/overview) to get started. The [GraphQL API](/api-reference/overview) and REST API v1 continue to work for now, but will be deprecated in a future release, so new integrations should build on API v2.
Expand Down
Loading