cve.bz

CVE-2026-107292 pydantic pydantic ai: Origin Validation Error

6.4 mediumEPSS 0.1%Fix available

Medium (6.4) in pydantic pydantic ai. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in pydantic-ai 1.107.5, 2.30.0.

On this page
Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 1.34.0 until 2.30.0, the Agent.to_web() and clai web development chat server does not validate the Host header, allowing a website visited by a developer to use DNS rebinding to reach a loopback-hosted agent as a same-origin service. The hostile page can read the served UI and submit chat requests that execute agent tools with the local process's privileges and credentials, causing data disclosure or unwanted side effects. Binding to localhost, Origin checks, and CSRF tokens do not prevent the same-origin DNS rebinding path. This issue is fixed in versions 1.107.5 and 2.30.0.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd 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-14. 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-346 Origin Validation Error
CWE-350 Reliance on Reverse DNS Resolution for a Security-Critical Action
OWASP Top 10
A07:2025 Authentication 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-107292 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107292?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107292?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-107292 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 1.34.0 before 1.107.5
pydantic:pydantic_aifrom 2.0.0 before 2.30.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q2xc-rrxj-58x9PyPIpydantic-ai>=1.34.0 <1.107.51.107.5
GHSA-q2xc-rrxj-58x9PyPIpydantic-ai>=2.0.0b1 <2.30.02.30.0
GHSA-q2xc-rrxj-58x9PyPIpydantic-ai-slim>=1.34.0 <1.107.51.107.5
GHSA-q2xc-rrxj-58x9PyPIpydantic-ai-slim>=2.0.0b1 <2.30.02.30.0
PYSEC-2026-4279PyPIpydantic-ai>=1.34.0 <1.107.5
>=2.0.0b1 <2.30.0
1.107.5, 2.30.0
PYSEC-2026-4288PyPIpydantic-ai-slim>=1.34.0 <1.107.5
>=2.0.0b1 <2.30.0
1.107.5, 2.30.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity flaw was found in the pydantic-ai development web chat UI (Agent.to_web() and clai web), which ships in Red Hat Enterprise Linux AI and Lightspeed Core container images. The chat server does not validate the HTTP Host header of incoming requests. If a developer who is running this local development server visits a malicious website, an attacker can use DNS rebinding to make the browser treat the loopback-hosted agent as a same-origin service; the hostile page can then read the served UI and submit chat requests that execute the agent's tools with the local process's privileges and credentials, potentially causing information disclosure and unwanted side effects. Binding the server to localhost, Origin header checks, and CSRF tokens do not prevent this attack path. Red Hat and upstream both rate this flaw moderate severity with a CVSS 3.1 base score of 6.4; successful exploitation requires user interaction and high attack complexity. All currently affected Red Hat products (Red Hat Enterprise Linux AI and Lightspeed Core) carry a DEFER resolution: because this is a moderate-impact flaw with a CVSS score below 7.0, no fix is currently scheduled for these products. The residual risk is limited to developers or applications serving the development web chat UI on a machine that is also used to browse untrusted websites, and the consequences depend on the tools the served agent exposes.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Binding the development web chat UI to localhost, Origin header checks, and CSRF tokens do not prevent the DNS rebinding attack path. Upstream resolved this issue by validating the Host header and rejecting unexpected hosts; the fix is available in pydantic-ai and pydantic-ai-slim 2.30.0, and in 1.107.5 on the v1 maintenance line.

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-107292.

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-89 Pharming Likelihood: High · Severity: Very High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-275 DNS Rebinding Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-346 (16).

References

Check your stackJSON