CVE-2026-77387

{"id": "CVE-2026-77387", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-77387", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-10-01T17:50:15.527973Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.0, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.5}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "geopy", "product": "geopy", "versions": [{"status": "affected", "version": "< 2.5.0"}]}]}], "published": "2026-10-01T17:17:31.733", "references": [{"url": "https://github.com/geopy/geopy/commit/5d09fa843f90ec80788b61552539c9fd3ae6c528", "source": "security-advisories@github.com"}, {"url": "https://github.com/geopy/geopy/issues/608", "source": "security-advisories@github.com"}, {"url": "https://github.com/geopy/geopy/pull/610", "source": "security-advisories@github.com"}, {"url": "https://github.com/geopy/geopy/releases/tag/2.5.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/geopy/geopy/security/advisories/GHSA-mhvh-fq92-pfmr", "source": "security-advisories@github.com"}, {"url": "https://github.com/geopy/geopy/issues/608", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-1333"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2026-10-02T18:04:10.850", "sourceIdentifier": "security-advisories@github.com"}