CVSS 4.0
2.3 lowCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NLow (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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Npydantic-ai (PyPI): fixed in 1.107.4, 2.27.1pydantic-ai-slim (PyPI): fixed in 1.107.4, 2.27.1Explain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| pydantic:pydantic_ai | from 0.3.4 before 1.107.4 |
| pydantic:pydantic_ai | from 2.0.0 before 2.27.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3gh4-cghq-f8v4 | PyPI | pydantic-ai | >=0.3.4 <1.107.4 | 1.107.4 |
| GHSA-3gh4-cghq-f8v4 | PyPI | pydantic-ai | >=2.0.0b1 <2.27.1 | 2.27.1 |
| GHSA-3gh4-cghq-f8v4 | PyPI | pydantic-ai-slim | >=0.3.4 <1.107.4 | 1.107.4 |
| GHSA-3gh4-cghq-f8v4 | PyPI | pydantic-ai-slim | >=2.0.0b1 <2.27.1 | 2.27.1 |
| PYSEC-2026-4274 | PyPI | pydantic-ai | >=0.3.4 <1.107.4 >=2.0.0b1 <2.27.1 | 1.107.4, 2.27.1 |
| PYSEC-2026-4283 | PyPI | pydantic-ai-slim | >=0.3.4 <1.107.4 >=2.0.0b1 <2.27.1 | 1.107.4, 2.27.1 |
Red Hat rates this Moderate.
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).
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Lightspeed Core | lightspeed-core/lightspeed-stack-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-cuda-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-gaudi-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-rocm-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/disk-image-cuda-rhel9 | Fix 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.