CVE-2026-48782

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. In versions 1.56.0 through 1.101.0, 2.0.0b1, and 2.0.0b2, the cloud-metadata blocklist could be bypassed by encoding the metadata IP in an IPv6 transition form that the previous fix, CVE-2026-46678, did not decode, exposing cloud IAM short-term credentials. The previous remediation decoded only IPv4-mapped IPv6, 6to4, and the NAT64 well-known prefix, so the metadata guarantee did not hold for the remaining transition forms: IPv4-compatible IPv6 (::a.b.c.d), the NAT64 RFC 8215 local-use prefix (64:ff9b:1::/48), operator-chosen NAT64 prefixes, and ISATAP. The IPv6 wrapper is then delivered to the underlying IPv4 metadata endpoint. This occurs when an application using Pydantic AI opts a URL into force_download='allow-local' (which disables the default block on private/internal IPs) and runs on a network that actually routes the affected IPv6 transition forms: NAT64-configured networks (IPv6-only or dual-stack-with-NAT64 deployments, including some Kubernetes setups) for the NAT64 variants, or networks with an ISATAP tunnel for ISATAP. A standard dual-stack cloud VM or container does not route these forms and is not affected in practice. The IPv4-compatible and Teredo variants are deprecated and addressed as defense-in-depth. This is an incomplete fix of GHSA-cqp8-fcvh-x7r3 / CVE-2026-46678 (itself a follow-up to CVE-2026-25580). This issue has been fixed in version 2.0.0b3.

CVSS v3
6.8
EG Score
6.8(medium)
EPSS
25.2%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Jun 18, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

SSRF cloud-metadata blocklist bypass via additional IPv6 transition forms · Advisory · pydantic/pydantic-ai · GitHub

https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-cg7w-rg45-pc59
github_release Patch Available

v1.102.0 (2026-05-22)

Patch available: pydantic/pydantic-ai v1.102.0

https://github.com/pydantic/pydantic-ai/releases/tag/v1.102.0
github_pr Patch Available

fix: expand IPv6 transition-form handling in URL validation

Patch available: pydantic/pydantic-ai v1.102.0 (PR #5596 merged 2026-05-23)

https://github.com/pydantic/pydantic-ai/pull/5596
github_commit Patch Available

commit 1add06179ba4 (pydantic/pydantic-ai)

Patch available: pydantic/pydantic-ai v1.102.0 (contains commit 1add06179ba4)

https://github.com/pydantic/pydantic-ai/commit/1add06179ba4de259f7ab977620b697b7209f7e4

Vendor Advisories for CVE-2026-48782(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 15:51 UTCEG score recompute
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 17:31 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 19:52 UTCEG score recompute
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 22:13 UTCEG score recompute
  9. 2026-07-03 00:34 UTCEG score recompute
  10. 2026-07-02 02:53 UTCEG score recompute
  11. 2026-07-01 15:07 UTCEPSS rescore
  12. 2026-07-01 05:15 UTCEG score recompute
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 07:36 UTCEG score recompute
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 09:56 UTCEG score recompute
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 12:17 UTCEG score recompute
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 14:37 UTCEG score recompute
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 16:58 UTCEG score recompute
  25. 2026-06-25 19:20 UTCEG score recompute
Show 25 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-24 21:40 UTCEG score recompute
  3. 2026-06-24 14:05 UTCEPSS rescore
  4. 2026-06-24 00:02 UTCEG score recompute
  5. 2026-06-23 21:33 UTCEPSS rescore
  6. 2026-06-23 21:33 UTCEPSS rescore
  7. 2026-06-23 02:23 UTCEG score recompute
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-22 04:45 UTCEG score recompute
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 06:59 UTCEG score recompute
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-20 09:14 UTCEG score recompute
  17. 2026-06-19 19:26 UTCEPSS rescore
  18. 2026-06-19 19:26 UTCEPSS rescore
  19. 2026-06-19 11:30 UTCEG score recompute
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 13:49 UTCEG score recompute
  23. 2026-06-17 17:53 UTCEPSS rescore
  24. 2026-06-17 16:05 UTCEG score recompute
  25. 2026-06-17 15:52 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48782?
CVE-2026-48782 is a medium vulnerability published on June 17, 2026. Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. In versions 1.56.0 through 1.101.0, 2.0.0b1, and 2.0.0b2, the cloud-metadata blocklist could be bypassed by encoding the metadata IP in an IPv6 transition form that the previous fix, CVE-2026-46678,…
When was CVE-2026-48782 disclosed?
CVE-2026-48782 was first published in the National Vulnerability Database on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48782 actively exploited?
CVE-2026-48782 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48782?
CVE-2026-48782 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-48782?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48782, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48782

Explore →

Is Your Infrastructure Affected by CVE-2026-48782?

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

Start Free Scan →Browse All CVEs