pantheon-ssrf-guard
A small, dependency-free SSRF egress guard for Python's standard-library HTTP client — one that survives DNS rebinding.
The guarantee: an outbound request cannot reach a private, loopback, link-local, cloud-metadata, or CGN address — even if the hostname resolves public at check time and rebinds to an internal IP before the socket connects.
Extracted from PANTHEON, a multi-tenant AI substrate, where it is the single canonical guard on every outbound path (link imports, uploaded-URL fetches, external MCP-server transports).
Why a pre-check isn't enough
The common "block internal hosts" approach resolves the hostname and rejects private IPs before connecting. An attacker defeats it with DNS rebinding: the name resolves to a public IP when you check it, then to 127.0.0.1 / 169.254.169.254 (cloud metadata) / an internal service by the time the socket actually opens.
pantheon-ssrf-guard uses two layers:
host_is_public(host)— the fast pre-check: reject if any resolved address is non-public.GuardedHTTP(S)Connection— at connect time, re-check the IP the socket actually reached. This is the layer a pre-check can't provide, and it's what closes the rebind window.
The classifier's catch-all is not ip.is_global, so it also rejects everything the obvious flags miss — RFC 6598 shared/CGN space (100.64.0.0/10, used by Kubernetes/internal load balancers and the Alibaba/Tencent/Oracle metadata endpoint 100.100.100.200), plus benchmark, documentation, and NAT64 ranges.
Install
pip install pantheon-ssrf-guard # or: copy the single ssrf_guard.py file into your project
Use
from ssrf_guard import guarded_opener, SsrfBlocked
opener = guarded_opener() # https-capable; redirects refused by default (each hop re-checked if allowed)
try:
with opener.open("https://example.com/data.json", timeout=10) as resp:
body = resp.read()
except SsrfBlocked:
... # the target resolved (or rebound) to a non-public address — refused before any data was sent
Lower-level pieces are exported too if you're building your own client:
from ssrf_guard import host_is_public, ip_is_public, peer_is_public
from ssrf_guard import GuardedHTTPHandler, GuardedHTTPSHandler
What it does not do
- It doesn't proxy, cache, or rate-limit — it only refuses non-public destinations.
- It guards
urllib/http.client. Forhttpx/requestsyou'd apply the same idea at their transport layer (the classification functions here are reusable). - It is not a WAF; it's the one specific control that stops server-side request forgery to internal infrastructure.
- Under DNS rebinding, a TLS handshake can reach the internal host before the peer check fires. For an ordinary private target (
http://127.0.0.1,https://192.168.1.1,169.254.169.254) nothing is attempted at all — the name check refuses before a socket exists, and the test suite asserts that nosocket.create_connectionoccurs. But if a public name resolves to a private address after that check,connect()completes the TCP+TLS handshake and the peer check refuses immediately afterwards. No request bytes are written and no response is read, so the attacker gets a handshake with an internal service, not a request to it. Eliminating even the handshake requires resolving the name yourself and connecting to a pinned IP — a different design, and one that breaks TLS hostname validation unless done carefully.
Changelog
-
0.2.0 — scheme allowlist at the opener boundary and environment proxies off by default, after an external review reproduced two bypasses:
build_opener()also installsfile:/ftp:/data:handlers, soopener.open("file:///etc/passwd")read a local file without the HTTP guard ever running; and aProxyHandlerinherited fromHTTP(S)_PROXYmoves the connection to the proxy, so the peer check validated the proxy while the real destination went unexamined. Now onlyhttp/httpsare reachable (enforced per-hop, so a redirect toftp:is refused too), the dangerous handlers are removed from the opener entirely, andProxyHandler({})is installed unless the caller passestrust_env_proxy=True. Also documents the DNS-rebinding handshake residue above, with tests pinning it. -
0.1.1 — the pre-check is now wired into the opener (so "two-layer" is true, not aspirational): a
GuardedHTTP(S)Connectionrejects a non-public host by name BEFORE opening the socket, then re-checks the actual peer at connect time (the rebind guard). And IPv4-mapped (::ffff:…) + NAT64 (64:ff9b::/96) addresses are normalised to their embedded v4 before classifying, so an internal target smuggled inside a v6 address is blocked version-independently instead of trusting whicheveris_*flags a given CPython sets. -
0.1.0 — initial release.
License
Apache-2.0. See LICENSE.
Release files for pantheon-ssrf-guard 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pantheon_ssrf_guard-0.2.1.tar.gz | 15.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pantheon_ssrf_guard-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.1 kB
Release files / pantheon_ssrf_guard-0.2.1.tar.gz
| Download URL | pantheon_ssrf_guard-0.2.1.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10b862f1b2e6c96378427f3f7ea1b6d6af0b3ab3c837829d3a8001ea928a3b88
|
|
BLAKE2b-256 checksum How to use checksums |
016106d6fac9408d112e7664a1806933a76f3fa3ea25a2fec1b191a841ebf2bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / pantheon_ssrf_guard-0.2.1-py3-none-any.whl
| Download URL | pantheon_ssrf_guard-0.2.1-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0188935984a3d090b735b5889d29976c082791757b766ed1be79f77b011ea25d
|
|
BLAKE2b-256 checksum How to use checksums |
80b59d6da42a392d98110913065955d75fa0f5d385d978353ec51ff18015e0d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency log