---
title: "CVE-2026-107295: Pydantic AI - Broken Access Control"
description: "Pydantic AI 1.34.0 to <1.107.4 and 2.28.0 contains a broken access control caused by missing request content-type validation in Agent.to_web() and clai chat endpoint, letting remote attackers execute tools with local process privileges, exploit requires attacker to submit crafted browser-compatible requests to loopback-hosted chat server."
url: https://panop.io/threat-heartbeat/CVE-2026-107295/
---

# CVE-2026-107295 Pydantic AI - Broken Access Control

Pydantic AI 1.34.0 to <1.107.4 and 2.28.0 contains a broken access control caused by missing request content-type validation in Agent.to\_web() and clai chat endpoint, letting remote attackers execute tools with local process privileges, exploit requires attacker to submit crafted browser-compatible requests to loopback-hosted chat server.

CVSS base score 7.6 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.16% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-107295)

## Details

Type

Broken Access Control

Impact

Privilege Escalation, Remote Code Execution

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L

Published

8 October 2026

Updated

15 October 2026

Weakness

[CWE-352](https://cwe.mitre.org/data/definitions/352.html)

## Vendor fix

Upgrade to versions 1.107.4 or 2.28.0 or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-107295](https://nvd.nist.gov/vuln/detail/CVE-2026-107295)
- [https://github.com/pydantic/pydantic-ai/pull/7383](https://github.com/pydantic/pydantic-ai/pull/7383)
- [https://github.com/pydantic/pydantic-ai/releases/tag/v1.107.4](https://github.com/pydantic/pydantic-ai/releases/tag/v1.107.4)
- [https://github.com/pydantic/pydantic-ai/releases/tag/v2.28.0](https://github.com/pydantic/pydantic-ai/releases/tag/v2.28.0)
- [https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-h4xc-3qfq-jf93](https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-h4xc-3qfq-jf93)
- [https://github.com/pydantic/pydantic-ai/commit/d2690201a1834005d382dbf5c47e0ed94ef8bf46](https://github.com/pydantic/pydantic-ai/commit/d2690201a1834005d382dbf5c47e0ed94ef8bf46)
- [https://github.com/pydantic/pydantic-ai/commit/dd2abbdfa029c9ad138e7cc0edd2eaeaf9ed69c0](https://github.com/pydantic/pydantic-ai/commit/dd2abbdfa029c9ad138e7cc0edd2eaeaf9ed69c0)
- [https://github.com/pydantic/pydantic-ai/pull/7382](https://github.com/pydantic/pydantic-ai/pull/7382)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
