CVE-2026-107293: Pydantic AI OpenTelemetry instrumentation: retry prompt content is not redacted when `include_content=False`
Noroxi assessment
Priority: Monitor (action score 9/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: pydantic-ai (PyPI) 1.107.4, 2.27.1; pydantic-ai-slim (PyPI) 1.107.4, 2.27.1.
Low priority for now. Upgrade to pydantic-ai (PyPI) 1.107.4, 2.27.1; pydantic-ai-slim (PyPI) 1.107.4, 2.27.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 8, 2026
- Updated
- Oct 13, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-212
Report tools
Action score
9
Monitor
Low priority for now.
- CVSS
- 9 / 40 · 2.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 2.3
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pydantic | pydantic ai | cpe:2.3:a:pydantic:pydantic_ai |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pydantic pydantic ai0.3.4 and later · before 1.107.4
- pydantic pydantic ai2.0.0 and later · before 2.27.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
pydantic pydantic-ai
- >= 0.3.4, < 1.107.4, >= 2.0.0b1, < 2.27.1affected
pydantic pydantic-ai-slim
- >= 0.3.4, < 1.107.4, >= 2.0.0b1, < 2.27.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | pydantic-ai | from 0.3.4 · before 1.107.4 | 1.107.4 |
| PyPI | pydantic-ai | from 2.0.0b1 · before 2.27.1 | 2.27.1 |
| PyPI | pydantic-ai-slim | from 0.3.4 · before 1.107.4 | 1.107.4 |
| PyPI | pydantic-ai-slim | from 2.0.0b1 · before 2.27.1 | 2.27.1 |
Same product
pydantic: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-25580Pydantic AI Affected by Server-Side Request Forgery (SSRF) in URL Download Handling34Monitor
- CVE-2026-107295`pydantic-ai-slim` web UI `/api/chat` accepts browser-simple cross-origin requests that can trigger agent tool execution30Monitor
- CVE-2026-107286Pydantic AI: Concurrency-limited models can keep their slot when a streamed request ends early30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-107291Oct 8, 2026 · Pydantic AI OpenTelemetry instrumentation: exception events on tool and agent run spans include content when `include_content=False`9Monitor
- ← EarlierCVE-2026-107292Oct 8, 2026 · Pydantic AI Web chat UI (`Agent.to_web()`, `clai web`): the local chat endpoint does not validate the `Host` header25Monitor
- Later →CVE-2026-107294Oct 8, 2026 · Pydantic AI: Unbounded memory use when downloading remote content via web_fetch or FileUrl26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:pydantic-ai | 1.107.4 | Package registry (OSV) |
| PyPI:pydantic-ai | 2.27.1 | Package registry (OSV) |
| PyPI:pydantic-ai-slim | 1.107.4 | Package registry (OSV) |
| PyPI:pydantic-ai-slim | 2.27.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 26, 2026+18 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1072910 days apartPydantic AI OpenTelemetry instrumentation: exception events on tool and agent run spans include content when `include_content=False`9Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-212 · Improper Removal of Sensitive Information Before Storage or TransferCVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
- Exploit maturity— → none
- SSVC exploitation— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.