geopy is a geocoding library for Python. Prior to 2.5.0, geopy.Point and Point.from_string() can spend excessive CPU time due to inefficient regular-expression behavior when an application passes a long malformed coordinate string without the 256-character input limit used by the fix. Geocoder reverse methods also reach the vulnerable parsing path when called with string inputs. Repeated attacker-controlled requests can cause a denial of service, while the numeric Point constructor is unaffected. This issue is fixed in version 2.5.0.
CVE-2026-77387
MEDIUMPre-NVD 4.04.0—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 4.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.0Exploit: Elevated riskExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 4.0
- EG Score
- 4.0MEDIUMmedium confidence
- EG Risk
- 34EG Risk 34/100CISA SSVC
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 computedSeverity40% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 9th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 1, 2026
Last Modified
October 2, 2026
Advisory Details (5)
Auto-updated Oct 1, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
2.5.0
Patch available: geopy/geopy 2.5.0
https://github.com/geopy/geopy/releases/tag/2.5.0github_commit Patch Available
commit 5d09fa843f90 (geopy/geopy)
Patch available: geopy/geopy 2.5.0 (contains commit 5d09fa843f90)
https://github.com/geopy/geopy/commit/5d09fa843f90ec80788b61552539c9fd3ae6c528github_pr Patch Available
Guard Point.from_string against ReDoS on very long inputs (#608)
Patch available: geopy/geopy 2.5.0 (PR #610 merged 2026-07-10)
https://github.com/geopy/geopy/pull/610generic Patch Available🟡 PoC Available
[Security] Regular Expression Denial of Service (ReDoS) in geopy.Point · Issue #608 · geopy/geopy · GitHub
https://github.com/geopy/geopy/issues/608github Patch Available
Regular Expression Denial of Service (ReDoS) in geopy.Point · Advisory · geopy/geopy · GitHub
https://github.com/geopy/geopy/security/advisories/GHSA-mhvh-fq92-pfmrVendor Advisories for CVE-2026-77387(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-10-03 18:51 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 18:15 UTCEG score recompute
- 2026-10-01 18:30 UTCEG score recompute
- 2026-10-01 17:59 UTCEG score recompute
- 2026-10-01 17:27 UTCEG score recompute
- 2026-10-01 16:51 UTCEG score recompute
- 2026-10-01 16:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-77387?
CVE-2026-77387 is a medium vulnerability published on October 1, 2026. geopy is a geocoding library for Python. Prior to 2.5.0, geopy.Point and Point.from_string() can spend excessive CPU time due to inefficient regular-expression behavior when an application passes a long malformed coordinate string without the 256-character input limit used by the fix. Geocoder…
When was CVE-2026-77387 disclosed?
CVE-2026-77387 was first published on October 1, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77387 actively exploited?
CVE-2026-77387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77387?
CVE-2026-77387 has a CVSS base score of 4.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77387?
A fix for CVE-2026-77387 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77387 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77387
Is Your Infrastructure Affected by CVE-2026-77387?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.