# CVE-2026-107293: Pydantic AI OpenTelemetry instrumentation: retry prompt content is not redacted when `include_content=False`

> Attackers with telemetry access can read sensitive validation feedback and model values from retry prompts when content redaction is enabled.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** CLEANSTART-2026-XD01399, GHSA-3gh4-cghq-f8v4, PYSEC-2026-4274, PYSEC-2026-4283

## What is CVE-2026-107293?

CVE-2026-107293 is a low-severity vulnerability in pydantic-ai, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 0.3.4 until 1.107.4 and 2.27.1, OpenTelemetry instrumentation configured with InstrumentationSettings(include_content=False) can export retry prompts outside tool calls in gen_ai.input.messages and pydantic_ai.all_messages. Agents using NativeOutput, PromptedOutput, or output validators on text output can therefore disclose validation feedback, including invalid model values quoted by that feedback, to readers of the telemetry backend. Tool-call retries and deployments that do not use include_content=False are not affected by this specific path. This issue is fixed in versions 1.107.4 and 2.27.1.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2026-107293?

10 open source packages ship an affected version, including pydantic-ai and pydantic-ai-slim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pydantic-ai` | PyPI | From 0.3.4 | 1.107.4, 2.27.1 |
| `pydantic-ai` | PyPI | From 0.3.4 | 1.107.4 |
| `pydantic-ai` | PyPI | From 0.3.4 | 1.107.4 |
| `pydantic-ai` | PyPI | From 2.0.0b1 | 2.27.1 |
| `pydantic-ai` | PyPI | From 2.0.0b1 | 2.27.1 |
| `pydantic-ai-slim` | PyPI | From 0.3.4 | 1.107.4, 2.27.1 |
| `pydantic-ai-slim` | PyPI | From 0.3.4 | 1.107.4 |
| `pydantic-ai-slim` | PyPI | From 0.3.4 | 1.107.4 |
| `pydantic-ai-slim` | PyPI | From 2.0.0b1 | 2.27.1 |
| `pydantic-ai-slim` | PyPI | From 2.0.0b1 | 2.27.1 |

Products: Pydantic Pydantic Ai.

## How do I fix CVE-2026-107293?

Upgrade pydantic-ai to a fixed version for your release line: 1.107.4 or 2.27.1.

## Is CVE-2026-107293 being exploited?

There is no known exploitation of CVE-2026-107293 in the wild and no public exploit code.

## Other vulnerabilities in pydantic-ai

- [CVE-2026-25580](https://insights.sbomify.com/CVE-2026-25580/): Pydantic AI Affected by Server-Side Request Forgery (SSRF) in URL Download Handling (high 8.6)
- [CVE-2026-107295](https://insights.sbomify.com/CVE-2026-107295/): Pydantic AI Web chat UI (`Agent.to_web()`, `clai web`): a website visited by the developer can trigger agent runs and server-side tool execution on the local chat endpoint (high 7.6)
- [CVE-2026-107286](https://insights.sbomify.com/CVE-2026-107286/): Pydantic AI: Concurrency-limited models can keep their slot when a streamed request ends early (high 7.5)
- [CVE-2026-25640](https://insights.sbomify.com/CVE-2026-25640/): Pydantic AI affected by Stored XSS via Path Traversal in Web UI CDN URL (high 7.1)
- [CVE-2026-107289](https://insights.sbomify.com/CVE-2026-107289/): Pydantic AI: SSRF cloud-metadata blocklist bypass via IPv6 zone identifiers (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107293 and fix it if it is affected.

What it is: CVE-2026-107293 is a low-severity vulnerability in pydantic-ai, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107293 in the wild and no public exploit code.

Affected packages and fixed versions:
- pydantic-ai (PyPI): affected from 0.3.4; fixed in 1.107.4, 2.27.1
- pydantic-ai (PyPI): affected from 0.3.4; fixed in 1.107.4
- pydantic-ai (PyPI): affected from 0.3.4; fixed in 1.107.4
- pydantic-ai (PyPI): affected from 2.0.0b1; fixed in 2.27.1
- pydantic-ai (PyPI): affected from 2.0.0b1; fixed in 2.27.1
- pydantic-ai-slim (PyPI): affected from 0.3.4; fixed in 1.107.4, 2.27.1
- pydantic-ai-slim (PyPI): affected from 0.3.4; fixed in 1.107.4
- pydantic-ai-slim (PyPI): affected from 0.3.4; fixed in 1.107.4
- pydantic-ai-slim (PyPI): affected from 2.0.0b1; fixed in 2.27.1
- pydantic-ai-slim (PyPI): affected from 2.0.0b1; fixed in 2.27.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107293/ (Markdown: https://insights.sbomify.com/CVE-2026-107293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107293
- OSV: https://osv.dev/vulnerability/CVE-2026-107293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107293/
Summaries are generated and may contain mistakes; the official description above is the record.