| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in geopandas up to 1.1.1. Affected is the function to_postgis. Executing a manipulation can lead to sql injection.
This vulnerability is registered as CVE-2025-69662. It is possible to launch the attack remotely. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical was found in geopandas up to 1.1.1. This vulnerability affects the function to_postgis. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at aydinnyunus.github.io. This vulnerability was named CVE-2025-69662 since 01/09/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
The vulnerability scanner Nessus provides a plugin with the ID 297413 (Linux Distros Unpatched Vulnerability : CVE-2025-69662), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 1.1.2 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (297413) and EUVD (EUVD-2025-206572). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 8.6
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 297413
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-69662
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: geopandas 1.1.2
Patch: github.com
Timeline
01/09/2026 CVE reserved01/31/2026 Advisory disclosed
01/31/2026 VulDB entry created
02/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: aydinnyunus.github.io
Status: Confirmed
CVE: CVE-2025-69662 (🔒)
GCVE (CVE): GCVE-0-2025-69662
GCVE (VulDB): GCVE-100-343540
EUVD: 🔒
Entry
Created: 01/31/2026 03:13Updated: 02/12/2026 02:12
Changes: 01/31/2026 03:13 (55), 01/31/2026 21:07 (2), 02/02/2026 00:16 (1), 02/12/2026 02:12 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.