CVSS 3.1
4.0 mediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LMedium (4.0) in geopy geopy. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in geopy 2.5.0.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lgeopy (PyPI): fixed in 2.5.0Explain CVE-2026-77387 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77387?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77387?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77387 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| geopy | < 2.5.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-mhvh-fq92-pfmr | PyPI | geopy | <2.5.0 | 2.5.0 |
| PYSEC-2026-4218 | PyPI | geopy | <2.5.0 | 2.5.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | geopy | no fix listed | DEBIAN-CVE-2026-77387 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | geopy | no fix listed | UBUNTU-CVE-2026-77387 |
| openSUSE | Tumbleweed | python-geopy | 2.5.0-1.1 | openSUSE-SU-2026:11724-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Moderate.
A MODERATE severity regular expression denial of service (ReDoS) flaw was found in geopy, a Python geocoding library bundled in Red Hat AI Inference Server and Red Hat Enterprise Linux AI (RHEL AI) container images. When an application passes a long, malformed coordinate string to geopy.Point or Point.from_string(), inefficient regular-expression evaluation consumes excessive CPU time, which can cause the application to hang or become unresponsive; geocoder reverse methods that accept string coordinates also reach the vulnerable parsing path. The numeric Point constructor is not affected. Red Hat and the upstream CVE record both rate this flaw MODERATE with a CVSS 3.1 score of 4.0 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), so there is no difference from the upstream severity. All currently affected Red Hat products (Red Hat AI Inference Server and RHEL AI) are resolved as DEFER: because this is an availability-only issue of moderate severity with a CVSS score below 7.0, no fix is currently planned for the bundled geopy dependency in these products. The residual risk is CPU resource exhaustion and temporary denial of service of the process that parses attacker-controlled coordinate strings; there is no impact on confidentiality or integrity.
Applications can mitigate this issue by validating and limiting the length of coordinate strings (for example, rejecting inputs longer than 256 characters, matching the limit adopted by the upstream fix) before passing them to geopy.Point, Point.from_string(), or geocoder reverse methods, and by preferring the numeric Point constructor, which is not affected. Restricting or rate-limiting the sources of externally supplied coordinate strings further reduces exposure. The upstream geopy project addressed this issue in version 2.5.0.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat AI Inference Server | rhaiis/vllm-cpu-rhel9 | Fix deferred | |
| Red Hat AI Inference Server | rhaiis/vllm-cuda-rhel9 | Fix deferred | |
| Red Hat AI Inference Server | rhaiis/vllm-tpu-rhel9 | Fix deferred | |
| Red Hat AI Inference Server | rhaii/vllm-cpu-rhel9 | Fix deferred | |
| Red Hat AI Inference Server | rhaii/vllm-cuda-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-aws-cuda-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-azure-cuda-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-cuda-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-gcp-cuda-rhel9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-77387.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.