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.
CVE-2026-107292
MEDIUMPre-NVD 6.46.4Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.4 from GitHub Security Advisory (severity: MODERATE) published 2026-10-08. A secondary CVSS source baseline 6.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-95099 (ENISA EUVD) · GHSA-q2xc-rrxj-58x9 (GitHub Security Advisories) · PYSEC-2026-4279 (OSV.dev) · PYSEC-2026-4288 (OSV.dev)Source: ENISA EUVD
6.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.1%CVSS: 6.4Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.4
- EG Score
- 6.4MEDIUMhigh confidence
- EG Risk
- 29EG Risk 29/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)Severity64% × 45%Impact severity (EG Severity): CVSS 6.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 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.1%
- EPSS %ILE
- 2nd
- 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 (6.4): severity, escalated by confirmed exploitation. This CVE's 6.4 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, and whom BOD 26-04 binds: 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.
The score's inputs: 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
October 8, 2026
Last Modified
October 14, 2026
Advisory Details (7)
Auto-updated Oct 8, 2026Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)
Web chat UI (`Agent.to_web()`, `clai web`): the local chat endpoint does not validate the `Host` header, so DNS rebinding can reach it from a website the developer visits · Advisory · pydantic/pydantic-ai · GitHub
https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-q2xc-rrxj-58x9GitHub release Patch Available
v2.30.0 (2026-08-13)
Patch available: pydantic/pydantic-ai v2.30.0
https://github.com/pydantic/pydantic-ai/releases/tag/v2.30.0GitHub release Patch Available
v1.107.5 (2026-08-13)
Patch available: pydantic/pydantic-ai v1.107.5
https://github.com/pydantic/pydantic-ai/releases/tag/v1.107.5GitHub pull request
Add `allowed_hosts` to `Agent.to_web()` and `clai web` (v1 backport)
Fix merged in pydantic/pydantic-ai PR #7438 on 2026-08-13 — awaiting tagged release
https://github.com/pydantic/pydantic-ai/pull/7438GitHub pull request Patch Available
Add `allowed_hosts` to `Agent.to_web()` and `clai web`
Patch available: pydantic/pydantic-ai v2.32.0 (PR #7437 merged 2026-08-13)
https://github.com/pydantic/pydantic-ai/pull/7437GitHub commit Patch Available
commit 871c7aeec5df (pydantic/pydantic-ai)
Patch available: pydantic/pydantic-ai v2.32.0 (contains commit 871c7aeec5df)
https://github.com/pydantic/pydantic-ai/commit/871c7aeec5dfed2138655ccbccbf15c6d763bae7GitHub commit
commit 394cc1d31656 (pydantic/pydantic-ai)
Fix landed in pydantic/pydantic-ai commit 394cc1d31656 — awaiting tagged release
https://github.com/pydantic/pydantic-ai/commit/394cc1d31656620704a703a2daed752afa5135feVendor Advisories for CVE-2026-107292(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | pydantic-ai @ 1.107.5 (fixes >= 1.34.0, < 1.107.5) | — | ghsa |
| pip | pydantic-ai @ 2.30.0 (fixes >= 2.0.0b1, < 2.30.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
PyPI(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pydantic-ai | 2.0.0 ... 2.9.1 (41 versions) |
| — |
| pydantic-ai-slim | 2.0.0 ... 2.9.1 (41 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 38× 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.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-11-01 08:00 UTCGHSA enrichmentGHSA-q2xc-rrxj-58x9 · GitHub severity MODERATE · GitHub CVSS 6.4
- 2026-11-01 08:00 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-27 12:25 UTCOSV refresh
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-25 14:54 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-18 05:07 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-14 01:27 UTCEG score recompute
- 2026-10-14 01:15 UTCEG score recompute
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 13 moreShow fewer
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:26 UTCEG score recompute
- 2026-10-11 15:00 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-10 21:49 UTCEG score recompute
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-09 21:14 UTCEG score recompute
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-08 17:26 UTCEG score recompute
- 2026-10-08 16:32 UTCEG score recomputeFirst assessed: 6.4 MEDIUM
- 2026-10-08 16:31 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:pydantic-ai
Frequently asked(5)
What is CVE-2026-107292?
CVE-2026-107292 is a medium-severity vulnerability; its CVE record was published on October 8, 2026. 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…
When was the CVE record for CVE-2026-107292 published?
The CVE record for CVE-2026-107292 was published on October 8, 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 October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-107292 actively exploited?
CVE-2026-107292 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107292?
CVE-2026-107292 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107292?
A fix for CVE-2026-107292 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107292 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107292
Is Your Infrastructure Affected by CVE-2026-107292?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.