Review reviewHigh

CVE-2026-25580

pydantic pydantic-ai, Red Hat Enterprise Linux AI (RHEL AI) 3, pydantic ai

Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 0.0.26 to before 1.56.0, aServer-Side Request Forgery (SSRF) vulnerability exists in Pydantic AI's URL download functionality. When applications accept message history from untrusted sources, attackers can include malicious URLs that cause the server to make HTTP requests to internal network resources, potentially accessing internal services or cloud credentials. This vulnerability only affects applications that accept message history from external users. This vulnerability is fixed in 1...

CVSS
8.6
EPSS
0.58%
44.4% percentile
CISA KEV
Not listed
Published
2026.02.07
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.58%
Technical severityCVSS 8.6

Vulnerability overview

Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 0.0.26 to before 1.56.0, aServer-Side Request Forgery (SSRF) vulnerability exists in Pydantic AI's URL download functionality. When applications accept message history from untrusted sources, attackers can include malicious URLs that cause the server to make HTTP requests to internal network resources, potentially accessing internal services or cloud credentials. This vulnerability only affects applications that accept message history from external users. This vulnerability is fixed in 1...

Affected product and versions

Product
pydantic pydantic-ai, Red Hat Enterprise Linux AI (RHEL AI) 3, pydantic ai
Affected versions
>= >= 0.0.26, < 1.56.0, >= 0.0.26 < 1.56.0
Fixed versions
1.56.0

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that pydantic pydantic-ai, Red Hat Enterprise Linux AI (RHEL AI) 3, pydantic ai and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
CWE
CWE-918