CVE-2021-29506 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in com.graphhopper:graphhopper-nav. A fix is available for com.graphhopper:graphhopper-nav — see the affected versions and patch details below.
Navigate endpoint is vulnerable to regex injection that may lead to Denial of Service.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-29506 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.graphhopper:graphhopper-navReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The regex injection that may lead to Denial of Service.
Patches
Will be patched in 2.4 and 3.0
Workarounds
Versions lower than 2.x are only affected if the navigation module is added
References
See this pull request for the fix: https://github.com/graphhopper/graphhopper/pull/2304
If you have any questions or comments about this advisory please send us an Email or create a topic here.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.graphhopper:graphhopper-nav | all versions | 2.4com.graphhopper:graphhopper-nav:2.4 |
Affected Products
graphhoppergraphhopperDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.graphhopper:graphhopper-nav, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.graphhopper:graphhopper-nav to 2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-29506 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2021-29506 in your dependencies?
Find it across Maven, including transitive dependencies.