Pydantic AI Web chat UI (`Agent.to_web()`, `clai web`): the local chat endpoint does not validate the `Host` header
pydantic-ai · pydantic-ai-slim
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| pydantic-ai PyPI |
|
|
| pydantic-ai-slim PyPI |
|
pydantic-ai · pydantic-ai-slim
| Product | Affected | Fixed in |
|---|---|---|
| pydantic-ai PyPI |
|
|
| pydantic-ai-slim PyPI |
|
|
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.
From the CVE record · GitHub_M
The Agent.to_web() and clai web development chat server does not validate the Host header. If a developer visits a hostile website while running a loopback-hosted agent, the site can use DNS rebinding to read the served UI and submit chat requests that run agent tools with the local process’s privileges and credentials.
Check deployments using PyPI pydantic-ai or pydantic-ai-slim versions >=1.34.0 <1.107.5 or >=2.0.0b1 <2.30.0.