cve.bz

CVE-2026-107293 pydantic pydantic ai

2.3 lowEPSS 0.3%Fix available

Low (2.3) in pydantic pydantic ai. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in pydantic-ai 1.107.4, 2.27.1.

On this page
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.

Severity

CVSS 4.0

2.3 low
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

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-212 Improper Removal of Sensitive Information Before Storage or Transfer
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-107293 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107293?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107293?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107293 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
pydantic:pydantic_aifrom 0.3.4 before 1.107.4
pydantic:pydantic_aifrom 2.0.0 before 2.27.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3gh4-cghq-f8v4PyPIpydantic-ai>=0.3.4 <1.107.41.107.4
GHSA-3gh4-cghq-f8v4PyPIpydantic-ai>=2.0.0b1 <2.27.12.27.1
GHSA-3gh4-cghq-f8v4PyPIpydantic-ai-slim>=0.3.4 <1.107.41.107.4
GHSA-3gh4-cghq-f8v4PyPIpydantic-ai-slim>=2.0.0b1 <2.27.12.27.1
PYSEC-2026-4274PyPIpydantic-ai>=0.3.4 <1.107.4
>=2.0.0b1 <2.27.1
1.107.4, 2.27.1
PYSEC-2026-4283PyPIpydantic-ai-slim>=0.3.4 <1.107.4
>=2.0.0b1 <2.27.1
1.107.4, 2.27.1

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate information disclosure vulnerability was found in the pydantic-ai Python agent framework, as shipped in Red Hat Enterprise Linux AI and Lightspeed Core. When pydantic-ai's OpenTelemetry instrumentation is configured with InstrumentationSettings(include_content=False) to suppress message content, retry prompts generated during output validation of agents that do not use tool calls — for example structured output via NativeOutput or PromptedOutput, or output validators applied to text output — are still exported to the telemetry backend in span attributes such as gen_ai.input.messages and pydantic_ai.all_messages. A user with read access to the telemetry logs or backend can therefore view validation feedback and invalid model values that were intended to be withheld. Deployments that do not use include_content=False, and retries tied to tool calls, are not affected by this path. Red Hat Enterprise Linux AI and Lightspeed Core are listed as affected; because the issue is rated moderate impact with a CVSS score below 7.0, fixes for the affected products are deferred, leaving the residual risk that message content meant to be suppressed continues to be exposed to readers of the telemetry backend until a fix is delivered. The upstream advisory rates this flaw as low severity (CVSS 2.3), which is lower than Red Hat's moderate rating (CVSS 4.3).

Red Hat's mitigation

Until the deferred fix is delivered, the exposure can be reduced by scrubbing or dropping the message attributes gen_ai.input.messages, gen_ai.output.messages, and pydantic_ai.all_messages in the telemetry pipeline, for example with an OpenTelemetry Collector processor, or by switching agents to tool-based structured output modes, whose retry feedback is correctly redacted when include_content=False. Previously exported traces can also be reviewed for retry prompt content that should not have been recorded. Upgrading pydantic-ai to a version containing the upstream fix (1.107.4 for the 1.x series or 2.27.1 for the 2.x series) resolves the issue.

ProductPackageStateAdvisory
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107293.

Attack patterns (CAPEC)

  • CAPEC-168 Windows ::DATA Alternate Data Stream Severity: Medium
  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON