PYSEC-2026-4218

Vulnerability from pysec - Published: 2026-10-15 10:22 - Updated: 2026-10-15 14:37
VLAI
Details

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.

Impacted products
Name purl
geopy pkg:pypi/geopy

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "geopy",
        "purl": "pkg:pypi/geopy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.5.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.92",
        "0.93",
        "0.94",
        "0.94.1",
        "0.94.2",
        "0.95",
        "0.95.1",
        "0.96.0",
        "0.96.1",
        "0.96.2",
        "0.96.3",
        "0.97",
        "0.97.1",
        "0.98",
        "0.98.1",
        "0.98.2",
        "0.98.3",
        "0.99",
        "1.0.0",
        "1.0.1",
        "1.1.0",
        "1.1.1",
        "1.1.2",
        "1.1.3",
        "1.1.4",
        "1.1.5",
        "1.10.0",
        "1.11.0",
        "1.12.0",
        "1.13.0",
        "1.14.0",
        "1.15.0",
        "1.16.0",
        "1.17.0",
        "1.18.0",
        "1.18.1",
        "1.19.0",
        "1.2.0",
        "1.20.0",
        "1.21.0",
        "1.22.0",
        "1.23.0",
        "1.3.0",
        "1.4.0",
        "1.5.0",
        "1.6.0",
        "1.6.1",
        "1.7.0",
        "1.7.1",
        "1.8.0",
        "1.8.1",
        "1.9.0",
        "1.9.1",
        "2.0.0",
        "2.0.0rc1",
        "2.1.0",
        "2.2.0",
        "2.3.0",
        "2.4.0",
        "2.4.1"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-77387",
    "GHSA-mhvh-fq92-pfmr"
  ],
  "details": "### Impact\n\n`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.\n\nGeocoders\u0027 `reverse` methods called with string inputs exercise the vulnerable path.\n\nApplications are affected when they pass attacker-controlled strings to these APIs without an appropriate length limit. Repeated requests may cause denial of service.\n\n### Patches\n\nFixed in geopy **2.5.0** by rejecting overly long (over 256 characters) coordinate strings before parsing.\n\n### Workarounds\n\nLimit coordinate strings to a reasonable maximum length, such as 256 characters, before passing them to geopy.",
  "id": "PYSEC-2026-4218",
  "modified": "2026-10-15T14:37:41.422153Z",
  "published": "2026-10-15T10:22:43.872971Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/geopy/geopy/security/advisories/GHSA-mhvh-fq92-pfmr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-77387"
    },
    {
      "type": "WEB",
      "url": "https://github.com/geopy/geopy/issues/608"
    },
    {
      "type": "WEB",
      "url": "https://github.com/geopy/geopy/pull/610"
    },
    {
      "type": "WEB",
      "url": "https://github.com/geopy/geopy/commit/5d09fa843f90ec80788b61552539c9fd3ae6c528"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/geopy/geopy"
    },
    {
      "type": "WEB",
      "url": "https://github.com/geopy/geopy/releases/tag/2.5.0"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/geopy"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-mhvh-fq92-pfmr"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "geopy: Regular Expression Denial of Service (ReDoS) in geopy.Point"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.