AI Stack Alert Medium CVE-2026-133505 For AppSec, AI Eng, SOC / IR AI-assisted
CVE-2026-133505: Pydantic AI message history deserialization can rebuild tool results as files
When Pydantic AI message history is serialized and loaded again, a tool result containing a JSON object in the serialized shape of a Pydantic AI file type is rebuilt as that file. A third party who controls data returned by a tool can cause the application to download a URL on its local network or make the model provider read an s3:// object or uploaded file using the application's credentials. The issue is fixed in pydantic-ai and pydantic-ai-slim 1.107.10 and 2.66.0.
Why it matters
Applications that store or reload message history containing third-party tool output may allow SSRF to internal URLs and unauthorized reads of cloud objects or uploaded files using the application's credentials.
Do this
- Upgrade pydantic-ai and pydantic-ai-slim to 1.107.10 or 2.66.0 or later.
- Identify applications where tool results can contain third-party data and message history is serialized and reloaded, including Temporal, DBOS or Prefect durable execution.
- Review whether stored or server-held message history is reloaded, and restrict outbound network access from the application to internal address ranges.
- Review credentials available to the application for S3 and uploaded file access and apply least privilege.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 5.9CVSS
- NoPublic PoC
- 26/100Priority
- 70%Confidence
Evidence
“The issue is fixed in pydantic-ai and pydantic-ai-slim 1.107.10 and 2.66.0.”
“can use this to make the application download a URL on its local network, or make the model provider read an s3:// object or uploaded file with the application's credentials.”
Sources
Affected / related
pydantic-ai, pydantic-ai-slim, Server-side request forgery
Published 2026-11-20 08:18 UTC · updated 2026-11-20 10:35 UTC · AI-assisted summary, checked against quoted sources · How we score