Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

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

CVE-2026-25580GHSA-2jrp-274c-jhv3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pydantic-ai 1.56.0; pydantic-ai-slim 1.56.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-25580: 0.65% estimated exploitation activity in the next 30 days; percentile 51.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery (SSRF) vulnerability exists in Pydantic AI's URL download functionality. When applications accept message history from untrusted sources, attackers can include malicious URLs that cause the server to make HTTP requests to internal network resources, potentially accessing internal services or cloud credentials. This vulnerability only affects applications that accept message history from external users, such as those using: - Agent.toweb or clai web to serve a chat interface - VercelAIAdapter for Vercel AI SDK integration - AGUIAdapter or Agent.toagui for AG-UI protocol integration - Custom APIs that accept message history from user input Applications that only use hardcoded or developer-controlled URLs are not affected. Description The downloaditem() helper function downloads content from URLs without validating that the target is a public internet address. When user-supplied message history contains URLs, attackers can: 1. Access internal…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2jrp-274c-jhv3

  2. Revision 1 · created ·

    Published from osv record GHSA-2jrp-274c-jhv3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25580

Advisory: Pydantic AI has Server-Side Request Forgery (SSRF) in URL Download Handling
IDs: CVE-2026-25580, GHSA-2jrp-274c-jhv3
Record: https://patchnext.com/advisories/cve-2026-25580 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pydantic-ai 1.56.0; pydantic-ai-slim 1.56.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pydantic-ai: affected >= 0.0.26, < 1.56.0; fixed in 1.56.0
- PyPI pydantic-ai-slim: affected >= 0.0.26, < 1.56.0; fixed in 1.56.0

## Suggested inspection (read-only)
- `python -m pip show pydantic-ai`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show pydantic-ai-slim`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pydantic-ai, pydantic-ai-slim.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2jrp-274c-jhv3 (OSV record GHSA-2jrp-274c-jhv3 lists affected ranges: PyPI pydantic-ai >=0.0.26 =0.0.26 <1.56.0 (fixed))
- Verified: https://github.com/advisories/GHSA-2jrp-274c-jhv3 (GitHub-reviewed advisory GHSA-2jrp-274c-jhv3 lists affected ranges: PyPI pydantic-ai >=0.0.26 =0.0.26 <1.56.0)

Commands are suggestions: review each one before running it.

Loading voting…