Vulnerability in pydantic-ai (CVE-2026-107291)
Summary
Vulnerability in pydantic-ai (CVE-2026-107291). Risk of unauthorized operations or information disclosure. Exploitable via ModelRetry. Mitigation: upgrade to 2.44.0 or later.
Original description
The description as published by the source.
Summary
Pydantic AI's OpenTelemetry instrumentation supports InstrumentationSettings(include_content=False) to exclude message content — user prompts, model completions, tool call arguments and responses, and any other message content — from exported telemetry, so that agents can be monitored without sending sensitive content to the observability backend.
The message attributes honoured the setting. Several other parts of the same spans did not, and exported content regardless of it:
- Exceptions. Recorded as OpenTelemetry exception events, with their message and stack trace, on tool, agent run, model request, embedding and image generation spans, and on realtime session spans. The message of the exception carrying a tool's
ModelRetryorToolFailedfeedback is the text sent back to the model, which can quote tool arguments and results. When a tool ran out of retries, the error that ended the run was chained from the last retry, so its stack trace repeated that text on the run span. Exceptions raised by tool code were recorded with their full message, as were failures of a model request, embedding or image generation, whose messages carry the provider's error response body. - The error status description. The OpenTelemetry SDK describes a span's ERROR status with the exception's type and message, so the message reached the backend a second time even where the event itself was redacted.
- Instructions and the prompted-output template. The `model_request…
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-107291 has been found in pydantic-ai.
Attackers can target a specific entry point like ModelRetry over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade pydantic-ai to 2.44.0 or later.
If unsure, ask your IT team or search "pydantic-ai CVE-2026-107291" on the vendor's site.
CVE-2026-107291 (pydantic-ai) — CWE-212 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ModelRetry / ToolFailed / model_request_parameters / gen_ai.input.messages
Patched: 2.44.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.
A vulnerability (CWE-212) exists in pydantic-ai. Attackers reach the vulnerable code path via ModelRetry.
Check the vendor advisory for the affected versions of pydantic-ai. Attack surface: ModelRetry / ToolFailed / model_request_parameters / gen_ai.input.messages.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.44.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.44.0ステージング環境で 2.44.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com