CVE-2026-107288: pydantic-ai · Server-Side Request Forgery (SSRF)
Affects pydantic-aiSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 2.44.0 or 1.107.6 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.44.0, 1.107.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade pydantic-ai and pydantic-ai-slim to 2.44.0 or 1.107.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pydanticpydantic-ai | Affected
| Fixed in
|
| pydanticpydantic-ai | Affected
| Fixed in
|
| pydanticpydantic-ai-slim | Affected
| Fixed in
|
| pydanticpydantic-ai-slim | Affected
| Fixed in
|
PyPIpydantic-aipkg:pypi/pydantic-aiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in pydantic-ai versions 1.107.6 and 2.44.0. Users should upgrade to these versions or later to remediate the issue. Since this is not a cloud service, remediation depends on applying the official patches. No additional mitigation steps are indicated by the vendor advisory.
Description
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.
References
- github.com/pydantic/pydantic-ai/security/advisories/GHSA-22h6-qm39-v87j (opens in a new tab)
- github.com/pydantic/pydantic-ai/pull/8407 (opens in a new tab)
- github.com/pydantic/pydantic-ai/pull/8409 (opens in a new tab)
- github.com/pydantic/pydantic-ai/pull/8421 (opens in a new tab)
- github.com/pydantic/pydantic-ai/commit/490335f8e2322e143a79337ddca9410e0176c812 (opens in a new tab)
- github.com/pydantic/pydantic-ai/commit/a9dab92099d0ef9d5d4aa34ccac8a6f1b0e51284 (opens in a new tab)
- github.com/pydantic/pydantic-ai/commit/c1f212a084cbfa0012f2044cdb4731d214b3b983 (opens in a new tab)
- github.com/pydantic/pydantic-ai/releases/tag/v1.107.6 (opens in a new tab)
- github.com/pydantic/pydantic-ai/releases/tag/v2.44.0 (opens in a new tab)