Advisory record · GHSA-2jrp-274c-jhv3

Pydantic AI has Server-Side Request Forgery (SSRF) in URL Download Handling

CVSS 8.6 HighEPSS 0.0065 · 51st percentile

Published by the GitHub Advisory Database at 6 Feb 2026, 18:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pydantic-aiPyPI>=0.0.26, <1.56.01.56.0
pydantic-ai-slimPyPI>=0.0.26, <1.56.01.56.0
Identifiers
GHSA-2jrp-274c-jhv3 · CVE-2026-25580 · PYSEC-2026-2976 · PYSEC-2026-2980
Weakness (CWE)
CWE-918
Published
6 Feb 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Pydantic AI (pydantic-ai and pydantic-ai-slim) versions from 0.0.26 before 1.56.0 are vulnerable to server-side request forgery in URL download handling. An attacker who can supply message history, such as through the web chat interface, Vercel AI or AG-UI adapters, or a custom API, can make the server fetch internal or cloud metadata URLs. Upgrade to version 1.56.0 or later, which blocks private addresses by default and always blocks cloud metadata endpoints.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0065, the 51st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:01 UTC First seen by agentprime
  2. 31 Oct 2026, 15:01 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.