CVE-2025-69662
SQL injection in geopandas <=1.1.1 via to_postgis writes to PostGIS
WAF coverage: SQL injection. Signatures match well at the request layer.
Also consider: parameterized queries · ORM
Is CVE-2025-69662 being exploited?
Not confirmed. CVE-2025-69662 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2025-69662?
CVE-2025-69662 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-69662?
Yes. A fix has been recorded for CVE-2025-69662. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-69662 affect?
CVE-2025-69662 affects Geopandas <= 1.1.1, to_postgis API, PostgreSQL with PostGIS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-69662?
Upgrade to geopandas >= 1.1.2
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SQLi via to_postgis can exfiltrate sensitive data from PostgreSQL/PostGIS
Patch when possible