CVE-2025-69662

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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, nvd
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

A fix is available — apply it.

SQL injection vulnerability in geopandas before v.1.1.2 allows an attacker to obtain sensitive information via the to_postgis()` function being used to write GeoDataFrames to a PostgreSQL database.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
70(Attend)
EG Risk 70/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

January 30, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated May 3, 2026
🔬 Proof of concept available. Patch available.
generic Patch Available

[SECURITY] [DLA 4523-1] python-geopandas security update

https://lists.debian.org/debian-lts-announce/2026/04/msg00025.html
generic

Fix SQL injection in to_postgis via geometry column name by aydinnyunus · Pull Request #3681 · geopandas/geopandas · GitHub

https://github.com/geopandas/geopandas/pull/3681
generic🟡 PoC Available

SQL Injection Vulnerability: Security Issue in GeoPandas to_postgis() Function | Yunus Aydın Blog

https://aydinnyunus.github.io/2025/12/27/sql-injection-geopandas/

Vendor Advisories for CVE-2025-69662(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-geopandas (1.0.1-2ubuntu0.1) @ questing2026-06-08ubuntu

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-geopandas0.8.2-10.8.2-1+deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-geopandas0.12.2-1 ... 1.1.4-1 (23 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-geopandas1.0.1-2 ... 1.1.4-1 (10 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-geopandas1.0.1-2, 1.1.0-1~exp1, 1.1.1-1, 1.1.1-1~exp1, 1.1.1-21.1.2-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
geopandas0.1.0 ... 1.1.1 (59 versions)1.1.2—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 42× 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.

Showing the most recent 100 of 169 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-69662?
CVE-2025-69662 is a high vulnerability published on January 30, 2026. SQL injection vulnerability in geopandas before v.1.1.2 allows an attacker to obtain sensitive information via the to_postgis()` function being used to write GeoDataFrames to a PostgreSQL database.
When was CVE-2025-69662 disclosed?
CVE-2025-69662 was first published in the National Vulnerability Database on January 30, 2026, with the most recent update 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-2025-69662 actively exploited?
CVE-2025-69662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.9% of all scored CVEs.
What is the CVSS score of CVE-2025-69662?
CVE-2025-69662 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-69662?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69662, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-69662

Explore →

Is Your Infrastructure Affected by CVE-2025-69662?

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

Start Free Scan →Browse All CVEs