CVE-2025-69662

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.4% (36th 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 weekElevated
8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

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.6HIGHmedium confidence
EG Risk
70
EG Risk 70/100

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 (value × EchelonGraph’s weight)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

January 30, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated May 3, 2026
Patch available.
Web pageMentions a patch (unverified)

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

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

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
Web page

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
python-geopandas0.8.2-1
  • every version up to 0.8.2-1+deb11u1: fixed in 0.8.2-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-geopandas0.12.2-1 ... 1.1.4-1 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-geopandas1.0.1-2 ... 1.1.4-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-geopandas1.0.1-2, 1.1.0-1~exp1, 1.1.1-1, 1.1.1-1~exp1, 1.1.1-2
  • every version up to 1.1.2-1: fixed in 1.1.2-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
geopandas0.1.0 ... 1.1.1 (59 versions)
  • every version up to 1.1.2: fixed in 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 12× in last 7d / 31× 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 96 of 209 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-69662?
CVE-2025-69662 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2025-69662 published?
The CVE record for CVE-2025-69662 was published on January 30, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-69662 actively exploited?
CVE-2025-69662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-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?
A fix for CVE-2025-69662 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-69662 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-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.

Book a Demo →Browse All CVEs