CVE-2021-23408 is a medium-severity (CVSS 4.3) CWE-1321 vulnerability in com.graphhopper:graphhopper-web-bundle. 1 public exploit reference exists, so weaponization risk is real. A fix is available for com.graphhopper:graphhopper-web-bundle — see the affected versions and patch details below.
Prototype Pollution in GraphHopper
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-23408 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 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-web-bundleReal-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
This affects the package com.graphhopper:graphhopper-web-bundle before 3.2, from 4.0-pre1 and before 4.0. The URL parser could be tricked into adding or modifying properties of Object.prototype using a constructor or proto payload.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.graphhopper:graphhopper-web-bundle | all versions | 3.2com.graphhopper:graphhopper-web-bundle:3.2 |
Affected Products
graphhoppergraphhopperResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.graphhopper:graphhopper-web-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.graphhopper:graphhopper-web-bundle to 3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23408 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2021-23408 in your dependencies?
Find it across Maven, including transitive dependencies.