# CVE-2026-54249: Pydantic AI: Unvalidated UploadedFile references in UI adapters allow server-side file access using the application's credentials

> Attackers can inject provider metadata to force the server to read arbitrary files from cloud storage using server-side credentials.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-h7p7-w5gc-xj3w, PYSEC-2026-3692, PYSEC-2026-3693

## What is CVE-2026-54249?

CVE-2026-54249 is a medium-severity server-side request forgery vulnerability in pydantic-ai, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pydantic AI is a Python agent framework for building Generative AI applications. In versions 1.65.0 through 1.105.0, and 2.0.0b1 through 2.0.0b5, a client that submits message history to a Pydantic AI UI adapter (such as the Vercel AI adapter) can reference arbitrary files in the application's model-provider or cloud-storage account. While file URL parts are validated against a scheme allowlist, UploadedFile references — which point to a file by provider file ID or cloud-storage URI (e.g. s3://…, gs://…) — were forwarded without validation. Because the provider resolves an UploadedFile using the server-side identity (IAM role, service account, or provider API key) rather than the client's, an attacker can craft message history to make the server read objects from its own account or other tenants, given a referenceable identifier. Exploitation requires a valid file identifier, which is not always unguessable depending on how the application names objects. This issue has been fixed in versions 1.106.0 and 2.0.0b6.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-54249?

10 open source packages ship an affected version, including pydantic-ai and pydantic-ai-slim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pydantic-ai` | PyPI | From 1.65.0 | 1.106.0, 2.0.0b6 |
| `pydantic-ai` | PyPI | From 1.65.0 | 1.106.0 |
| `pydantic-ai` | PyPI | From 1.65.0 | 1.106.0 |
| `pydantic-ai` | PyPI | From 2.0.0b1 | 2.0.0b6 |
| `pydantic-ai` | PyPI | From 2.0.0b1 | 2.0.0b6 |
| `pydantic-ai-slim` | PyPI | From 1.65.0 | 1.106.0, 2.0.0b6 |
| `pydantic-ai-slim` | PyPI | From 1.65.0 | 1.106.0 |
| `pydantic-ai-slim` | PyPI | From 1.65.0 | 1.106.0 |
| `pydantic-ai-slim` | PyPI | From 2.0.0b1 | 2.0.0b6 |
| `pydantic-ai-slim` | PyPI | From 2.0.0b1 | 2.0.0b6 |

Products: Pydantic Pydantic Ai.

## How do I fix CVE-2026-54249?

Upgrade pydantic-ai to a fixed version for your release line: 1.106.0 or 2.0.0b6.

## Is CVE-2026-54249 being exploited?

There is no known exploitation of CVE-2026-54249 in the wild and no public exploit code.

## Other vulnerabilities in pydantic-ai

- [CVE-2026-25580](https://insights.sbomify.com/CVE-2026-25580/): Pydantic AI Affected by Server-Side Request Forgery (SSRF) in URL Download Handling (high 8.6)
- [CVE-2026-107295](https://insights.sbomify.com/CVE-2026-107295/): Pydantic AI Web chat UI (`Agent.to_web()`, `clai web`): a website visited by the developer can trigger agent runs and server-side tool execution on the local chat endpoint (high 7.6)
- [CVE-2026-107286](https://insights.sbomify.com/CVE-2026-107286/): Pydantic AI: Concurrency-limited models can keep their slot when a streamed request ends early (high 7.5)
- [CVE-2026-25640](https://insights.sbomify.com/CVE-2026-25640/): Pydantic AI affected by Stored XSS via Path Traversal in Web UI CDN URL (high 7.1)
- [CVE-2026-107289](https://insights.sbomify.com/CVE-2026-107289/): Pydantic AI: SSRF cloud-metadata blocklist bypass via IPv6 zone identifiers (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54249 and fix it if it is affected.

What it is: CVE-2026-54249 is a medium-severity server-side request forgery vulnerability in pydantic-ai, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54249 in the wild and no public exploit code.

Affected packages and fixed versions:
- pydantic-ai (PyPI): affected from 1.65.0; fixed in 1.106.0, 2.0.0b6
- pydantic-ai (PyPI): affected from 1.65.0; fixed in 1.106.0
- pydantic-ai (PyPI): affected from 1.65.0; fixed in 1.106.0
- pydantic-ai (PyPI): affected from 2.0.0b1; fixed in 2.0.0b6
- pydantic-ai (PyPI): affected from 2.0.0b1; fixed in 2.0.0b6
- pydantic-ai-slim (PyPI): affected from 1.65.0; fixed in 1.106.0, 2.0.0b6
- pydantic-ai-slim (PyPI): affected from 1.65.0; fixed in 1.106.0
- pydantic-ai-slim (PyPI): affected from 1.65.0; fixed in 1.106.0
- pydantic-ai-slim (PyPI): affected from 2.0.0b1; fixed in 2.0.0b6
- pydantic-ai-slim (PyPI): affected from 2.0.0b1; fixed in 2.0.0b6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54249/ (Markdown: https://insights.sbomify.com/CVE-2026-54249/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54249
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54249
- OSV: https://osv.dev/vulnerability/CVE-2026-54249

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54249/
Summaries are generated and may contain mistakes; the official description above is the record.