CVE-2026-25640

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-5593 (ENISA EUVD) · PYSEC-2026-2979 (OSV.dev) · PYSEC-2026-2983 (OSV.dev)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 1.34.0 to before 1.51.0, a path traversal vulnerability in the Pydantic AI web UI allows an attacker to serve arbitrary JavaScript in the context of the application by crafting a malicious URL. In affected versions, the CDN URL is constructed using a version query parameter from the request URL. This parameter is not validated, allowing path traversal sequences that cause the server to fetch and serve attacker-controlled HTML/JavaScript from an arbitrary source on the same CDN, instead of the legitimate chat UI package. If a victim clicks the link or visits it via an iframe, attacker-controlled code executes in their browser, enabling theft of chat history and other client-side data. This vulnerability only affects applications that use Agent.to_web to serve a chat interface and clai web to serve a chat interface from the CLI. These are typically run locally (on localhost), but may also be deployed on a remote server. This vulnerability is fixed in 1.51.0.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 6, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jul 19, 2026
Patch available. Sources: github_release, github, redhat.
Red Hat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25640.json
Red Hat

2437753 – (CVE-2026-25640) CVE-2026-25640 Pydantic AI: Pydantic AI: Arbitrary code execution and information disclosure via path traversal in web UI

https://bugzilla.redhat.com/show_bug.cgi?id=2437753
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-25640
GitHub advisoryMentions a patch (unverified)

Stored XSS via Path Traversal in Web UI CDN URL · Advisory · pydantic/pydantic-ai · GitHub

https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-wjp5-868j-wqv7
GitHub release Patch Available

v1.51.0 (2026-01-30)

Patch available: pydantic/pydantic-ai v1.51.0

https://github.com/pydantic/pydantic-ai/releases/tag/v1.51.0

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
pydantic-ai1.34.0 ... 1.50.0 (17 versions)
  • 1.34.0 up to 1.51.0: fixed in 1.51.0
—
pydantic-ai-slim1.34.0 ... 1.50.0 (17 versions)
  • 1.34.0 up to 1.51.0: fixed in 1.51.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-31 01:25 UTCOSV refresh
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-25 14:39 UTCEG score recompute
  10. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-23 04:30 UTCEG score recompute
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-18 03:52 UTCEG score recompute
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-12 16:19 UTCEG score recompute
Show 73 more
  1. 2026-10-11 20:01 UTCEG score recompute
  2. 2026-10-11 17:14 UTCEG score recompute
  3. 2026-10-11 14:46 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  8. 2026-10-08 16:54 UTCOSV refresh
  9. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  11. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  12. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-09-18 22:53 UTCOSV refresh
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  23. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  26. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  27. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  28. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  29. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  36. 2026-08-31 02:21 UTCOSV refresh
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  38. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  39. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  41. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  42. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  50. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  51. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-08-14 10:58 UTCEG score recompute
  53. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  54. 2026-08-13 03:17 UTCEG score recompute
  55. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  56. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-08-09 15:38 UTCEG score recompute
  59. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  61. 2026-08-07 22:36 UTCEG score recompute
  62. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-08-06 04:15 UTCEG score recompute
  64. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  65. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  66. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  67. 2026-08-02 21:14 UTCEG score recompute
  68. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  69. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  70. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  71. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  72. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  73. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-25640?
CVE-2026-25640 is a medium-severity vulnerability; its CVE record was published on February 6, 2026. Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. From 1.34.0 to before 1.51.0, a path traversal vulnerability in the Pydantic AI web UI allows an attacker to serve arbitrary JavaScript in the context of the application by crafting a malicious URL.…
When was the CVE record for CVE-2026-25640 published?
The CVE record for CVE-2026-25640 was published on February 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-25640 actively exploited?
CVE-2026-25640 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25640?
CVE-2026-25640 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-25640?
A fix for CVE-2026-25640 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25640

Explore →

Is Your Infrastructure Affected by CVE-2026-25640?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs