← Back
CVE-2026-54249 medium CVSS 6.8

SSRF (Server-Side Request Forgery) in pydantic-ai-slim (CVE-2026-54249)

Summary

SSRF in pydantic-ai-slim (CVE-2026-54249). Confidential information can be exposed externally. Exploitable via ``UploadedFile``. Mitigation: upgrade to `2.0.0b6` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-54249** has been found in pydantic-ai-slim. Attackers can target a specific entry point like ``UploadedFile`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 6.8/10. What to do: upgrade pydantic-ai-slim to **2.0.0b6** or later. If unsure, ask your IT team or search "pydantic-ai-slim CVE-2026-54249" on the vendor's site.
CVE-2026-54249 (pydantic-ai-slim) — CWE-918 / CVSS v3 6.8 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `UploadedFile` Patched: `2.0.0b6` — apply immediately Workaround: If users cannot upgrade, do not pass untrusted client-submitted message history to the agent, or strip `UploadedFile` parts from incoming messages before running the agent. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in pydantic-ai-slim. Attackers reach the vulnerable code path via ``UploadedFile`` without authentication.
📍 Affected scope
pydantic-ai-slim — . Attack surface: `UploadedFile`.
🔥 Severity
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.0.0b6**.
🛡️ Workaround
Workaround: If users cannot upgrade, do not pass untrusted client-submitted message history to the agent, or strip `UploadedFile` parts from incoming messages before running the agent.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pydantic-ai-slim' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'pydantic-ai-slim' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pydantic-ai-slim` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate
    If users cannot upgrade, do not pass untrusted client-submitted message history to the agent, or strip `UploadedFile` parts from incoming messages before running the agent.

    パッチが適用されるまでの応急処置として、If users cannot upgrade, do not pass untrusted client-submitted message history to the agent, or strip `UploadedFile` parts from incoming messages before running the agent. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade pydantic-ai-slim to 2.0.0b6

    ステージング環境で 2.0.0b6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip pydantic-ai-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0b6"}]}]
pip pydantic-ai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0b6"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →