CVE-2026-54249

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.8
EG Score
6.8(medium)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 4, 2026

Advisory Details (1)

Auto-updated Jul 29, 2026
Patch available. Sources: github.
github Patch Available

VercelAIAdapter trusts client-controlled `providerMetadata` to construct `UploadedFile` — S3/GCS confused deputy via provider metadata injection · Advisory · pydantic/pydantic-ai · GitHub

https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-h7p7-w5gc-xj3w

Vendor Advisories for CVE-2026-54249(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFixed inDependents
pydantic-ai1.100.0 ... 2.0.0b5 (52 versions)2.0.0b6—
pydantic-ai-slim1.100.0 ... 2.0.0b5 (52 versions)2.0.0b6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-16 06:38 UTCEG score recompute
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 07:45 UTCEG score recompute
  4. 2026-09-14 03:06 UTCEG score recompute
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 04:14 UTCEG score recompute
  7. 2026-09-12 05:19 UTCEG score recompute
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 06:27 UTCEG score recompute
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-09 07:44 UTCEG score recompute
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-07 20:36 UTCEG score recompute
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 10:22 UTCEG score recompute
  17. 2026-09-05 11:30 UTCEG score recompute
  18. 2026-09-04 11:53 UTCEG score recompute
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 22:45 UTCEG score recompute
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-30 22:02 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 58 more
  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:06 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-27 10:37 UTCEG score recompute
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-26 11:42 UTCEG score recompute
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 12:51 UTCEG score recompute
  10. 2026-08-24 13:57 UTCEG score recompute
  11. 2026-08-22 16:14 UTCEG score recompute
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 17:22 UTCEG score recompute
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 19:38 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 20:40 UTCEG score recompute
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 21:48 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 22:48 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 23:56 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 02:12 UTCEG score recompute
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 03:21 UTCEG score recompute
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 04:29 UTCEG score recompute
  31. 2026-08-11 05:37 UTCEG score recompute
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-10 06:45 UTCEG score recompute
  34. 2026-08-09 13:46 UTCEPSS rescore
  35. 2026-08-09 07:53 UTCEG score recompute
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-08 09:02 UTCEG score recompute
  38. 2026-08-07 10:10 UTCEG score recompute
  39. 2026-08-06 13:47 UTCEPSS rescore
  40. 2026-08-06 11:18 UTCEG score recompute
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-05 12:27 UTCEG score recompute
  43. 2026-08-04 15:10 UTCEPSS rescore
  44. 2026-08-04 13:26 UTCEG score recompute
  45. 2026-08-04 10:39 UTCEPSS rescore
  46. 2026-08-03 14:37 UTCEG score recompute
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 15:46 UTCEG score recompute
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 16:54 UTCEG score recompute
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-30 19:09 UTCEG score recompute
  53. 2026-07-30 16:28 UTCEPSS rescore
  54. 2026-07-30 14:38 UTCEG score recompute
  55. 2026-07-30 13:21 UTCEG score recompute
  56. 2026-07-29 21:22 UTCEG score recompute
  57. 2026-07-29 20:43 UTCEG score recompute
  58. 2026-07-29 20:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54249?
CVE-2026-54249 is a medium vulnerability published on July 29, 2026. 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…
When was CVE-2026-54249 disclosed?
CVE-2026-54249 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54249 actively exploited?
CVE-2026-54249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.3% of all scored CVEs.
What is the CVSS score of CVE-2026-54249?
CVE-2026-54249 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-54249?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54249, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54249

Explore →

Is Your Infrastructure Affected by CVE-2026-54249?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs