CVE-2026-107289 json
Pydantic AI: SSRF cloud-metadata blocklist bypass via IPv6 zone identifier (incomplete fix for CVE-2026-46678 and CVE-2026-48782)
published last mo. modified 25d ago also EUVD-2026-95077 , GHSA-vmxc-h2x2-jmf3 , PYSEC-2026-4282 , PYSEC-2026-4291
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi pydantic-ai 1.107.6, 2.44.0
- pypi pydantic-ai-slim 1.107.6, 2.44.0
- pydantic pydantic_ai 1.107.6, 2.44.0
- pydantic pydantic_ai_slim 1.107.6, 2.44.0
- github.com/pydantic/pydantic-ai@02157e1 commit
- github.com/pydantic/pydantic-ai@4da7059 commit
- github.com/pydantic/pydantic-ai#8401 pull request
- github.com/pydantic/pydantic-ai#8402 pull request
- github.com/pydantic/pydantic-ai/releases/tag/v1.107.6 release
- github.com/pydantic/pydantic-ai/releases/tag/v2.44.0 release
Is CVE-2026-107289 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-107289 updated cvss 3.7
pydantic-ai: pydantic-ai: Information disclosure via cloud metadata blocklist bypass
-
Red Hat Lightspeed Core lightspeed-core/lightspeed-stack-rhel9 Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/pydantic/pydantic-ai/pull/8401 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/pydantic/pydantic-ai/commit/02157e1b87bd45d3f2e111ce07afdf89f9fb0e5b referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/pydantic/pydantic-ai/commit/4da70591460f51a8c4f128eaeef70a33340dbd55 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-vmxc-h2x2-jmf3 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N |
| GitHub | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N |
| OSV | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pydantic-ai | >=1.56.0, <1.107.6 >=2.0.0b1, <2.44.0 |
1.107.6 2.44.0 |
| pypi | pydantic-ai-slim | >=1.56.0, <1.107.6 >=2.0.0b1, <2.44.0 |
1.107.6 2.44.0 |
Affected products
- pydantic pydantic-ai
- pydantic pydantic-ai-slim
Classification
References
-
github.com
/pydantic/pydantic-ai/pull/8401
web, exploit, patch, vendor-advisory
-
github.com
/pydantic/pydantic-ai/pull/8402
web, patch, vendor-advisory
-
github.com
/pydantic/pydantic-ai/commit/02157e1b87bd45d3f2e111ce07afdf89f9fb0e5b
web, exploit, patch
-
github.com
/pydantic/pydantic-ai/commit/4da70591460f51a8c4f128eaeef70a33340dbd55
web, exploit, patch
-
github.com
/pydantic/pydantic-ai/releases/tag/v1.107.6
web, patch, release-notes, vendor-advisory
-
github.com
/pydantic/pydantic-ai/releases/tag/v2.44.0
web, patch, release-notes, vendor-advisory
-
github.com
/pydantic/pydantic-ai/security/advisories/GHSA-vmxc-h2x2-jmf3
web, exploit, mitigation, vendor-advisory
-
github.com
/pydantic/pydantic-ai
package
-
pypi.org
/project/pydantic-ai
package
-
github.com
/advisories/GHSA-vmxc-h2x2-jmf3
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-107289
advisory
-
pypi.org
/project/pydantic-ai-slim
package
Sources
- CVE List CVE-2026-107289
- GitHub Advisory GHSA-vmxc-h2x2-jmf3
- NVD CVE-2026-107289
- OSV PYSEC-2026-4282
- OSV PYSEC-2026-4291
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.