Vulnerability in geopy (CVE-2026-77387)
Summary
Vulnerability in geopy (CVE-2026-77387). Risk of unauthorized operations or information disclosure. Exploitable via geopy.Point. Mitigation: upgrade to 2.5.0 or later.
Original description
The description as published by the source.
Impact
geopy.Point and Point.from_string() may take excessive CPU time when parsing long, malformed coordinate strings due to inefficient regular-expression behavior. The numeric Point constructor is not affected.
Geocoders' reverse methods called with string inputs exercise the vulnerable path.
Applications are affected when they pass attacker-controlled strings to these APIs without an appropriate length limit. Repeated requests may cause denial of service.
Patches
Fixed in geopy 2.5.0 by rejecting overly long (over 256 characters) coordinate strings before parsing.
Workarounds
Limit coordinate strings to a reasonable maximum length, such as 256 characters, before passing them to geopy.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-77387 has been found in geopy.
Attackers can target a specific entry point like geopy.Point over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.0/10.
What to do: upgrade geopy to 2.5.0 or later.
If unsure, ask your IT team or search "geopy CVE-2026-77387" on the vendor's site.
CVE-2026-77387 (geopy) — CWE-1333 / CVSS v3 4.0
Attack vector: local / unauthenticated / no user interaction
Attack surface: geopy.Point / reverse
Patched: 2.5.0 — apply immediately
Workaround: Limit coordinate strings to a reasonable maximum length, such as 256 characters, before passing them to geopy.
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.
A vulnerability (CWE-1333) exists in geopy. Attackers reach the vulnerable code path via geopy.Point without authentication.
Check the vendor advisory for the affected versions of geopy. Attack surface: geopy.Point / reverse.
Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.
Update to 2.5.0.
Workaround: Limit coordinate strings to a reasonable maximum length, such as 256 characters, before passing them to geopy.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'geopy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'geopy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
geopyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Limit coordinate strings to a reasonable maximum length, such as 256 characters, before passing them to geopy.パッチが適用されるまでの応急処置として、Limit coordinate strings to a reasonable maximum length, such as 256 characters, before passing them to geopy. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade geopy to 2.5.0ステージング環境で 2.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com