UTC
Low

Pydantic AI OpenTelemetry instrumentation: retry prompt content is not redacted when `include_content=False`

CVE-2026-107293 · GHSA-3gh4-cghq-f8v4 · published 2026-10-08

Severity
Low
CVSS score
2.3
Chance of exploitation (EPSS)
0.30%
Fixed in
2.27.1
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

This does not grant an attacker any new access to the agent or its data: the content is only visible to whoever can read the exported telemetry. The exposure matters when traces are exported to a destination whose audience is broader or less trusted than the agent's own data — a third-party observability vendor or a shared backend — which is the scenario include_content=False exists for. The disclosed content is limited to retry feedback: validation error details, which can quote invalid values from the model's output, or output-validator ModelRetry messages.

What to do

Upgrade pydantic-ai to 2.27.1 or later, and pydantic-ai-slim to 2.27.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Upgrade to a patched version; retry prompt content now honors include_content=False like all other message content. If you rely on this setting, consider reviewing previously exported traces for retry prompt content that should not have been recorded.

If you cannot upgrade yet

If you cannot upgrade, scrub or drop the message attributes (gen_ai.input.messages, gen_ai.output.messages, pydantic_ai.all_messages) in your telemetry pipeline (for example with an OpenTelemetry Collector processor), or use tool-based structured output modes, whose retry feedback honors include_content=False.

Affected
PackageRegistryAffectedFixed in
pydantic-aiPyPI>= 0.3.4, < 1.107.41.107.4
pydantic-aiPyPI>= 2.0.0b1, < 2.27.12.27.1
pydantic-ai-slimPyPI>= 0.3.4, < 1.107.41.107.4
pydantic-ai-slimPyPI>= 2.0.0b1, < 2.27.12.27.1

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].