Cross-Site Request Forgery (CSRF) in pydantic-ai (CVE-2026-107295)
Summary
Vulnerability in pydantic-ai (CVE-2026-107295). Data can be tampered with by attackers. Mitigation: upgrade to 2.28.0 or later.
Original description
The description as published by the source.
Summary
The Pydantic AI development web chat UI (Agent.to_web(), clai web) did not check the content type of requests to its chat endpoint. This allowed a website visited by a developer to submit a request to a chat UI running on that developer's machine, causing the served agent to run and to execute its tools with the privileges and credentials of the local process.
Binding the web UI to localhost — the default — does not prevent this, because a page open in the developer's browser can reach the loopback address.
Impact
Applications and developers serving an agent through Agent.to_web() or clai web. The consequences depend on the tools the served agent exposes, and can include data disclosure as well as unwanted tool side effects. Tools marked requires_approval=True were not protected either, because the endpoint trusts approval decisions relayed by the client.
Mitigation
Upgrade to a patched version. The chat endpoint now requires Content-Type: application/json and rejects other requests before the request body is parsed and before the agent runs. The bundled chat UI already sends this header; scripts and other non-browser clients that call the endpoint directly may need to be updated to send it.
If you cannot upgrade, don't run the web UI while browsing untrusted sites, stop it when you aren't using it, and don't serve an agent with side-effecting tools through it.
Credits
- Thai Son Dinh from VinSOC Labs (R&D)
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107295 has been found in pydantic-ai.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: upgrade pydantic-ai to 2.28.0 or later.
If unsure, ask your IT team or search "pydantic-ai CVE-2026-107295" on the vendor's site.
CVE-2026-107295 (pydantic-ai) — CWE-352 / CVSS v3 7.6
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.28.0 — apply immediately
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.
CSRF (CWE-352) exists in pydantic-ai.
Check the vendor advisory for the affected versions of pydantic-ai.
Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.
Update to 2.28.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pydantic-ai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pydantic-ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pydantic-aiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pydantic-ai to 2.28.0ステージング環境で 2.28.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。