cve.bz

CVE-2026-77387 geopy geopy

4.0 mediumEPSS 0.2%Fix available

Medium (4.0) in geopy geopy. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in geopy 2.5.0.

On this page
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.

Severity

CVSS 3.1

4.0 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1333 Inefficient Regular Expression Complexity
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
geopy< 2.5.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mhvh-fq92-pfmrPyPIgeopy<2.5.02.5.0
PYSEC-2026-4218PyPIgeopy<2.5.02.5.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14geopyno fix listedDEBIAN-CVE-2026-77387
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moregeopyno fix listedUBUNTU-CVE-2026-77387
openSUSETumbleweedpython-geopy2.5.0-1.1openSUSE-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

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat AI Inference Serverrhaiis/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-cuda-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-tpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-cpu-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-aws-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-azure-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gcp-cuda-rhel9Fix 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.

Attack patterns (CAPEC)

  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON