Pydantic AI: SSRF cloud-metadata blocklist bypass via IPv4-mapped IPv6 (Incomplete fix of CVE-2026-25580)
pydantic-ai · pydantic-ai-slim
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| pydantic-ai PyPI |
|
|
| pydantic-ai-slim PyPI |
|
|
pydantic-ai · pydantic-ai-slim
| Product | Affected | Fixed in |
|---|---|---|
| pydantic-ai PyPI |
|
|
| pydantic-ai-slim PyPI |
|
|
Pydantic AI is a Python agent framework for building Generative AI applications. In versions 1.56.0 through 1.98.0, when an application opts a URL into force_download='allow-local' (disabling the default block on private/internal IPs), the cloud-metadata blocklist could be bypassed by encoding the metadata IP in an IPv6 transition form (IPv4-mapped IPv6, 6to4, or NAT64), exposing cloud IAM short-term credentials on dual-stack or translated networks. This is an incomplete fix of GHSA-2jrp-274c-jhv3 / CVE-2026-25580, whose remediation did not hold for IPv6-encoded forms of the metadata IPs. An application is affected only if it explicitly opts a FileUrl (ImageUrl, AudioUrl, VideoUrl, DocumentUrl) into force_download='allow-local' on a URL influenced by untrusted input; it is not affected when using bundled integrations to ingest user input (Agent.to_web / clai web, VercelAIAdapter, AGUIAdapter / Agent.to_ag_ui), since they do not propagate force_download from external data, nor when downloading only from developer-controlled URLs. This issue has been fixed in version 1.99.0.
From the CVE record · GitHub_M
The cloud-metadata blocklist in Pydantic AI can be bypassed using IPv6 transition forms of a metadata IP. An attacker who controls a URL can potentially expose cloud IAM short-term credentials on dual-stack or translated networks, but only if the application explicitly uses force_download='allow-local' for that URL.
Check applications using PyPI pydantic-ai or pydantic-ai-slim versions 1.56.0 through 1.98.0 with force_download='allow-local' on untrusted URLs.