CVE-2026-54249: Pydantic AI — MEDIUM

Q: Is CVE-2026-54249 actively exploited?

No confirmed active exploitation of CVE-2026-54249 has been reported, but organizations should still patch proactively.

Q: How to fix CVE-2026-54249?

Update to patched version: Pydantic AI 1.106.0, Pydantic AI 1.106.0.

Q: What is the CVSS score for CVE-2026-54249?

CVE-2026-54249 has a CVSS v3.1 base score of 6.8 (MEDIUM). The EPSS exploitation probability is 0.20%.

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...

Full CISO analysis pending enrichment.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
Pydantic AI	pip	>= 1.65.0, < 1.106.0	`1.106.0`
19.2K 483 dependents Pushed 5d ago 92% patched ~189d to patch Full package profile →
Pydantic AI	pip	>= 1.65.0, < 1.106.0	`1.106.0`
19.2K 483 dependents Pushed 5d ago 92% patched ~189d to patch Full package profile →

How severe is it?

CVSS 3.1

6.8 / 10

EPSS

0.2%

chance of exploitation in 30 days

Higher than 10% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

N/A

What is the attack surface?

AV Network

AC High

PR None

UI None

S Changed

C High

I None

A None

What should I do?

Patch available

Update Pydantic AI to version 1.106.0

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-54249?

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.

Is CVE-2026-54249 actively exploited?

No confirmed active exploitation of CVE-2026-54249 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-54249?

Update to patched version: Pydantic AI 1.106.0, Pydantic AI 1.106.0.

What is the CVSS score for CVE-2026-54249?

CVE-2026-54249 has a CVSS v3.1 base score of 6.8 (MEDIUM). The EPSS exploitation probability is 0.20%.

What are the technical details?

Original Advisory

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.

Weaknesses (CWE)

CWE-918 Server-Side Request Forgery (SSRF) Primary CWE-918 Server-Side Request Forgery (SSRF) Primary CWE-918 Server-Side Request Forgery (SSRF)

CWE-918 — Server-Side Request Forgery (SSRF): The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Source: MITRE CWE corpus.