CVSS 3.1
7.6 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:LHigh (7.6) in pydantic pydantic ai. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in pydantic-ai 1.107.4, 2.28.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:Lpydantic-ai (PyPI): fixed in 1.107.4, 2.28.0pydantic-ai-slim (PyPI): fixed in 1.107.4, 2.28.0Explain CVE-2026-107295 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107295?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107295?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-107295 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 1.34.0 before 1.107.4 |
| pydantic:pydantic_ai | from 2.0.0 before 2.28.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-h4xc-3qfq-jf93 | PyPI | pydantic-ai | >=1.34.0 <1.107.4 | 1.107.4 |
| GHSA-h4xc-3qfq-jf93 | PyPI | pydantic-ai | >=2.0.0b1 <2.28.0 | 2.28.0 |
| GHSA-h4xc-3qfq-jf93 | PyPI | pydantic-ai-slim | >=1.34.0 <1.107.4 | 1.107.4 |
| GHSA-h4xc-3qfq-jf93 | PyPI | pydantic-ai-slim | >=2.0.0b1 <2.28.0 | 2.28.0 |
| PYSEC-2026-4278 | PyPI | pydantic-ai | >=1.34.0 <1.107.4 >=2.0.0b1 <2.28.0 | 1.107.4, 2.28.0 |
| PYSEC-2026-4287 | PyPI | pydantic-ai-slim | >=1.34.0 <1.107.4 >=2.0.0b1 <2.28.0 | 1.107.4, 2.28.0 |
Red Hat rates this Important.
An IMPORTANT severity flaw was found in the pydantic-ai-slim Python package, which is included in Red Hat Lightspeed Core (the lightspeed-stack-rhel9 container). The local development web chat interface (Agent.to_web() and the clai web endpoint) does not validate the Content-Type of requests to its chat endpoint. A remote attacker can host a malicious website that, when visited by a developer while the chat server is running on their machine, submits a browser-compatible cross-origin request to the loopback-hosted server, causing the served agent to run and execute its tools with the privileges and credentials of the local process. Because the endpoint trusts approval decisions relayed by the client, tools marked requires_approval=True are not protected either. Binding the server to localhost does not prevent this attack, since a page open in the developer's browser can reach the loopback address. The affected Lightspeed Core streams (lightspeed-core-0.6 and lightspeed-core-0.7) are resolved as DELEGATED, and a fix is being pursued with the maintaining team. Red Hat's severity rating matches the upstream assessment.
The upstream project has released a fix and recommends upgrading to a patched version of pydantic-ai-slim, in which the chat endpoint requires a Content-Type: application/json header and rejects other requests before the request body is parsed and before the agent runs. If upgrading is not immediately possible, the following upstream guidance reduces the risk: do not run the development web chat UI (Agent.to_web() or clai web) while browsing untrusted websites, stop the web UI when it is not in use, and do not serve an agent with side-effecting tools through it.
| Product | Package | State | Advisory |
|---|---|---|---|
| Lightspeed Core | lightspeed-core/lightspeed-stack-rhel9 | Affected |
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-107295.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.