VercelAIAdapter trusts client-controlled `providerMetadata` to construct `UploadedFile` — S3/GCS confused deputy via provider metadata injection
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.106.0, 2.0.0b6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- pydantic pydantic-ai
From 1.65.0 · fixed in 1.106.0; From 2.0.0b1 · fixed in 2.0.0b6
- pydantic pydantic-ai-slim
From 2.0.0b1 · fixed in 2.0.0b6; From 1.65.0 · fixed in 1.106.0
- pydantic-aiPyPI
From 1.65.0 · fixed in 1.106.0; From 2.0.0b1 · fixed in 2.0.0b6
- pydantic-ai-slimPyPI
From 1.65.0 · fixed in 1.106.0; From 2.0.0b1 · fixed in 2.0.0b6
- pydantic-ai-slimPyPI
From 1.65.0 · fixed in 1.106.0
- pydantic-ai-slimPyPI
From 2.0.0b1 · fixed in 2.0.0b6
- pydantic-aiPyPI
From 1.65.0 · fixed in 1.106.0
- pydantic-aiPyPI
From 2.0.0b1 · fixed in 2.0.0b6