CVE-2026-107289: Pydantic AI: SSRF cloud-metadata blocklist bypass via IPv6 zone identifier (incomplete fix for CVE-2026-46678 and CVE-2026-48782)
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: pydantic-ai (PyPI) 1.107.6, 2.44.0; pydantic-ai-slim (PyPI) 1.107.6, 2.44.0.
Low priority for now. Upgrade to pydantic-ai (PyPI) 1.107.6, 2.44.0; pydantic-ai-slim (PyPI) 1.107.6, 2.44.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 8, 2026
- Updated
- Oct 13, 2026
- EPSS
- 0.3% · 33th percentile
- CWE
- CWE-918
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pydantic | pydantic ai | cpe:2.3:a:pydantic:pydantic_ai |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
pydantic pydantic-ai
- >= 1.56.0, < 1.107.6, >= 2.0.0b1, < 2.44.0affected
pydantic pydantic-ai-slim
- >= 1.56.0, < 1.107.6, >= 2.0.0b1, < 2.44.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pydantic pydantic ai1.56.0 and later · before 1.107.6
- pydantic pydantic ai2.0.0 and later · before 2.44.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | pydantic-ai | from 1.56.0 · before 1.107.6 | 1.107.6 |
| PyPI | pydantic-ai | from 2.0.0b1 · before 2.44.0 | 2.44.0 |
| PyPI | pydantic-ai-slim | from 1.56.0 · before 1.107.6 | 1.107.6 |
| PyPI | pydantic-ai-slim | from 2.0.0b1 · before 2.44.0 | 2.44.0 |
Same product
pydantic: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-25580Pydantic AI Affected by Server-Side Request Forgery (SSRF) in URL Download Handling34Monitor
- CVE-2026-107295`pydantic-ai-slim` web UI `/api/chat` accepts browser-simple cross-origin requests that can trigger agent tool execution30Monitor
- CVE-2026-107286Pydantic AI: Concurrency-limited models can keep their slot when a streamed request ends early30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-107287Oct 8, 2026 · Pydantic AI: Excessive resource use when local web fetching converts nested HTML26Monitor
- ← EarlierCVE-2026-107288Oct 8, 2026 · Pydantic AI: web_fetch_tool blocked_domains bypass via a hostname the resolver normalizes differently14Monitor
- Later →CVE-2026-107290Oct 8, 2026 · Pydantic AI: Event loop blocked by quadratic title extraction in `web_fetch`26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:pydantic-ai | 1.107.6 | Package registry (OSV) |
| PyPI:pydantic-ai | 2.44.0 | Package registry (OSV) |
| PyPI:pydantic-ai-slim | 1.107.6 | Package registry (OSV) |
| PyPI:pydantic-ai-slim | 2.44.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+36 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-25580244 days apartPydantic AI Affected by Server-Side Request Forgery (SSRF) in URL Download Handling34Monitor
- CVE-2026-5424971 days apartVercelAIAdapter trusts client-controlled `providerMetadata` to construct `UploadedFile` — S3/GCS confused deputy via provider metadata injection27Monitor
- CVE-2026-48782113 days apartpydantic-ai: SSRF blocklist bypass via IPv4-compatible, SIIT/IVI, and local NAT64 IPv6 addresses (incomplete fix of CVE-2026-46678)27Monitor
- CVE-2026-4667871 days apartPydantic AI: SSRF cloud-metadata blocklist bypass via IPv4-mapped IPv6 (Incomplete fix of CVE-2026-25580)23Monitor
- CVE-2026-1072880 days apartPydantic AI: web_fetch_tool blocked_domains bypass via a hostname the resolver normalizes differently14Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
- Exploit maturity— → none
- SSVC exploitation— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.