Pydantic AI: SSRF cloud-metadata blocklist bypass via IPv6 zone identifier (incomplete fix for CVE-2026-46678 and CVE-2026-48782)
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 applications and workflows with Generative AI. From 1.56.0 until 1.107.6 and 2.44.0, applications that opt attacker-influenced URLs into local network access through FileUrl with force_download='allow-local' or web_fetch_tool with allow_local_urls=True can bypass the cloud-metadata blocklist by appending an IPv6 zone identifier to an IPv6 metadata address. IPv6Address equality and hashing include the zone identifier, so the blocklist comparison fails even though the network stack ignores the zone on a non-link-local destination and reaches the metadata service, potentially exposing cloud IAM credentials. The opt-in settings are disabled by default, and the issue requires an IPv6-enabled environment. This issue is fixed in versions 1.107.6 and 2.44.0.
From the CVE record · GitHub_M
Pydantic AI and pydantic-ai-slim can fail to block cloud metadata addresses when an attacker-influenced URL includes an IPv6 zone identifier. In an IPv6-enabled environment, this could expose cloud IAM credentials if an application enables local URL access through FileUrl or web_fetch_tool; those settings are disabled by default.
Check applications using PyPI pydantic-ai or pydantic-ai-slim versions >=1.56.0 <1.107.6 or >=2.0.0b1 <2.44.0.