cve.bz

CVE-2026-107286 pydantic pydantic ai

7.5 highEPSS 0.4%Fix available

High (7.5) in pydantic pydantic ai. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in pydantic-ai 2.53.0.

On this page
Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 2.10.0 until 2.53.0, streamed requests made through ConcurrencyLimitedModel or limit_model_concurrency can retain shared concurrency slots because anyio.CapacityLimiter associates an acquired slot with the borrowing task while streaming cleanup can run in a different task. Early stream termination, cancellation, consumer exceptions, or complete stream_text() consumption with debounce_by=0.1 can therefore leave capacity occupied, eventually preventing later requests that share the long-lived limiter from proceeding and causing a denial of service. Agent-level max_concurrency and non-streaming model requests are not affected. This issue is fixed in version 2.53.0.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th 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: yes · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-772 Missing Release of Resource after Effective Lifetime
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-107286 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107286?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107286?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-107286 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 2.10.0 before 2.53.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6fqq-452j-qhrpPyPIpydantic-ai>=2.10.0 <2.53.02.53.0
GHSA-6fqq-452j-qhrpPyPIpydantic-ai-slim>=2.10.0 <2.53.02.53.0
PYSEC-2026-4276PyPIpydantic-ai>=2.10.0 <2.53.02.53.0
PYSEC-2026-4285PyPIpydantic-ai-slim>=2.10.0 <2.53.02.53.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

An IMPORTANT severity denial-of-service flaw was found in pydantic-ai, a Python agent framework for building generative AI applications, which is shipped in Red Hat Enterprise Linux AI and Lightspeed Core. When streamed requests are processed through model-level concurrency limiting (ConcurrencyLimitedModel or limit_model_concurrency), shared concurrency slots acquired from anyio.CapacityLimiter can fail to be released when a stream is terminated early, cancelled, or encounters an exception, because the capacity limiter associates an acquired slot with the borrowing task while streaming cleanup can run in a different task. A remote attacker without authentication or user interaction can exploit this flaw by repeatedly initiating and abandoning streaming operations to permanently exhaust the shared concurrency capacity, preventing subsequent requests that share the long-lived limiter from being processed and causing a denial of service. Agent-level max_concurrency and non-streaming model requests are not affected. The Red Hat severity rating of IMPORTANT (CVSS 7.5) matches the upstream rating. Red Hat Enterprise Linux AI and Lightspeed Core ship the affected pydantic-ai package and are listed as affected, and fixes for these products are being pursued.

Red Hat's mitigation

Applications using pydantic-ai can avoid this issue by not applying model-level concurrency limiting to streamed requests: configure concurrency limits through the agent-level max_concurrency setting or use non-streaming model requests, as those code paths are not affected. Where possible, upgrading to pydantic-ai 2.53.0 or later, which contains the upstream fix, is recommended. For Red Hat Enterprise Linux AI and Lightspeed Core, apply the updated containers and packages when they become available through the respective product releases.

ProductPackageStateAdvisory
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Affected

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

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON