SSRF (Server-Side Request Forgery) in Pydantic AI (CVE-2026-107288)
Summary
SSRF in Pydantic AI (CVE-2026-107288). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 1.77.0 until 1.107.6 and 2.44.0, the local web_fetch_tool and the WebFetch local fallback compare blocked_domains entries with a URL hostname before both values are normalized to the form used by getaddrinfo. An attacker-influenced model can use an equivalent IDNA spelling, non-ASCII label separator, case variation, or trailing root label that resolves to a blocked host but does not match the configured string, causing the application to fetch that host with its own privileges. allowed_domains fails closed for unmatched spellings, and private-IP and cloud-metadata protections remain effective. This issue is fixed in versions 1.107.6 and 2.44.0.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107288 has been found in Pydantic AI.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Pydantic AI CVE-2026-107288" on the vendor's site.
CVE-2026-107288 (Pydantic AI) — CWE-918 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in Pydantic AI.
Check the vendor advisory for the affected versions of Pydantic AI.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Pydantic AI を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com