What is CVE-2026-77387?

CVE-2026-77387 is a medium-severity inefficient regular expression (ReDoS) vulnerability in geopy (pip), affecting versions <= 2.4.1. It is fixed in 2.5.0. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.

How severe is CVE-2026-77387?

CVE-2026-77387 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of geopy are affected by CVE-2026-77387?

geopy (pip) versions <= 2.4.1 is affected.

Is there a fix for CVE-2026-77387?

Yes. CVE-2026-77387 is fixed in 2.5.0. Upgrade to this version or later.

Is CVE-2026-77387 exploitable, and should I be worried?

Whether CVE-2026-77387 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-77387 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-77387?

Upgrade geopy to 2.5.0 or later.

CVE-2026-77387 in geopy

Q: How severe is CVE-2026-77387?

CVE-2026-77387 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of geopy are affected by CVE-2026-77387?

geopy (pip) versions <= 2.4.1 is affected.

Q: Is there a fix for CVE-2026-77387?

Yes. CVE-2026-77387 is fixed in 2.5.0. Upgrade to this version or later.

Q: Is CVE-2026-77387 exploitable, and should I be worried?

Whether CVE-2026-77387 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-77387 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-77387?

Upgrade geopy to 2.5.0 or later.

Summary

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

Workarounds

Limit coordinate strings to a reasonable maximum length, such as 256 characters, before passing them to geopy.

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.

A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use. Typical impact: denial of service when input is crafted to trigger backtracking.

CVE-2026-77387 has a CVSS score of 4.0 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.0); upgrading removes the vulnerable code path.

Affected versions

geopy (<= 2.4.1)

Security releases

geopy → 2.5.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Fixed in geopy 2.5.0 by rejecting overly long (over 256 characters) coordinate strings before parsing.

Frequently Asked Questions

What is CVE-2026-77387? CVE-2026-77387 is a medium-severity inefficient regular expression (ReDoS) vulnerability in geopy (pip), affecting versions <= 2.4.1. It is fixed in 2.5.0. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.
How severe is CVE-2026-77387? CVE-2026-77387 has a CVSS score of 4.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of geopy are affected by CVE-2026-77387? geopy (pip) versions <= 2.4.1 is affected.
Is there a fix for CVE-2026-77387? Yes. CVE-2026-77387 is fixed in 2.5.0. Upgrade to this version or later.
Is CVE-2026-77387 exploitable, and should I be worried? Whether CVE-2026-77387 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-77387 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-77387? Upgrade geopy to 2.5.0 or later.