Valhalla is an open source routing engine and accompanying libraries for use with OpenStreetMap data. In 3.7.0 and earlier, a POST request to /sources_to_targets containing an exclude_polygons ring formed by three collinear points can cause unbounded memory growth in the worker. The zero-area geometry, rather than the other request options, triggers processing in src/loki/polygon_search.cc until the process is terminated by the out-of-memory killer. A single unauthenticated request can therefore stop a public-facing worker. Other endpoints that accept exclude_polygons, including /route, were not verified as affected. No fixed version is available as of this review.
CVE-2026-54716
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
September 17, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 17, 2026Degenerate exclude_polygons (collinear points, zero area) causes OOM in /sources_to_targets · Advisory · valhalla/valhalla · GitHub
https://github.com/valhalla/valhalla/security/advisories/GHSA-qpf6-xp29-pg6rWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 16:36 UTCEG score recompute
- 2026-09-19 04:02 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 15:26 UTCEG score recompute
- 2026-09-18 14:54 UTCEG score recompute
- 2026-09-17 20:18 UTCEG score recompute
- 2026-09-17 19:51 UTCEG score recompute
- 2026-09-17 19:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-54716?
When was CVE-2026-54716 disclosed?
Is CVE-2026-54716 actively exploited?
What is the CVSS score of CVE-2026-54716?
How do I remediate CVE-2026-54716?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54716
Is Your Infrastructure Affected by CVE-2026-54716?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.