PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-77387 geopy CVE debrief

The CVE record was published on 2026-10-02T22:38:14.000Z and has not been modified since then. The NVD entry is currently null. This CVE affects applications using geopy, particularly those passing attacker-controlled strings to geopy APIs without length limits, which may lead to denial of service through excessive CPU time consumption. Defenders should assess exposure and prioritize remediation by verifying geopy versions and updating to 2.5.0 or later if vulnerable. Implementing length limits for coordinate strings can mitigate the issue.

Vendor
geopy
Product
Unknown
CVSS
MEDIUM 4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-02
Original CVE updated
2026-10-15
Advisory published
2026-10-02
Advisory updated
2026-10-15

Who should care

Defenders responsible for applications using geopy, particularly those passing attacker-controlled strings to geopy APIs without length limits, should assess exposure and prioritize remediation.

Why it matters

CVE-2026-77387 is a Regular Expression Denial of Service (ReDoS) vulnerability in geopy.Point. Defenders should verify geopy versions, update to 2.5.0 or later if vulnerable, and implement length limits for coordinate strings to prevent denial of service risks.

  • Denial of service through repeated requests with malformed coordinate strings
  • Potential for excessive CPU time consumption leading to performance degradation
  • Need for verification of geopy versions and implementation of coordinate string length limits

Technical summary

The geopy library is vulnerable to a Regular Expression Denial of Service (ReDoS) attack in the geopy.Point class. This occurs when parsing long, malformed coordinate strings due to inefficient regular-expression behavior. The issue is fixed in geopy 2.5.0, which rejects overly long coordinate strings before parsing. The vulnerability affects geopy versions prior to 2.5.0, where the numeric Point constructor is not affected but 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, potentially leading to denial of service through repeated requests.

Defensive priority

Defenders should prioritize verifying geopy versions and updating to 2.5.0 or later if vulnerable. Limiting coordinate string lengths can mitigate the issue.

Recommended defensive actions

  • Verify geopy versions in use and update to 2.5.0 or later if vulnerable
  • Implement length limits for coordinate strings to prevent excessive CPU time
  • Review applications using geopy for potential denial of service risks
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The source corpus provides details on the Regular Expression Denial of Service (ReDoS) vulnerability in geopy.Point. It mentions that the issue is fixed in geopy 2.5.0 and suggests limiting coordinate strings to a reasonable maximum length as a workaround.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-77387 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-77387

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-77387 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-77387

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • geopy: Regular Expression Denial of Service (ReDoS) in geopy.Point

    Unverified legacy reference

    URL: https://storage.googleapis.com/osv-vulnerabilities/PyPI/GHSA-mhvh-fq92-pfmr.json

    osv_dev

  • Source reference

    Unverified legacy reference

    URL: https://github.com/geopy/geopy/security/advisories/GHSA-mhvh-fq92-pfmr

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://github.com/geopy/geopy/issues/608

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://github.com/geopy/geopy/pull/610

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://github.com/geopy/geopy/commit/5d09fa843f90ec80788b61552539c9fd3ae6c528

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://github.com/geopy/geopy

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://github.com/geopy/geopy/releases/tag/2.5.0

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.