← Back
CVE-2025-69662
Vulnerability in geopandas (CVE-2025-69662)
Summary
vulnerability in geopandas (CVE-2025-69662). Confidential information can be exposed externally. Mitigation: upgrade to `1.1.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-69662** has been found in geopandas.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade geopandas to **1.1.2** or later.
If unsure, ask your IT team or search "geopandas CVE-2025-69662" on the vendor's site.
CVE-2025-69662 (geopandas) — CWE-202 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.1.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-202) exists in geopandas.
📍 Affected scope
geopandas — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.1.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'geopandas' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'geopandas' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `geopandas` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade geopandas to 1.1.2ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
geopandas
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]
pip
geopandas
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-69662
- advisory https://github.com/advisories/GHSA-6497-prx7-gpmq
- package https://github.com/geopandas/geopandas
- patch https://github.com/geopandas/geopandas/pull/3681
- report https://aydinnyunus.github.io/2025/12/27/sql-injection-geopandas/
- web https://github.com/geopandas/geopandas/issues/3679
- web https://github.com/geopandas/geopandas/commit/6aa8ef14ffdee4ba1044349ab948e1a1fbfaf419
- web https://aydinnyunus.github.io/2025/12/27/sql-injection-geopandas
- web https://github.com/geopandas/geopandas/releases/tag/v1.1.2
- web https://lists.debian.org/debian-lts-announce/2026/04/msg00025.html
- web https://github.com/pypa/advisory-database/tree/main/vulns/geopandas/PYSEC-2026-62.yaml