find-my-way: DDoS with HTTP2
### Impact Remotely triggerable DoS in find-my-way when it is used with Node's HTTP/2 server. The short version is that `lookup()` passes `req.method` into `find()`, and `find()` indexes `this.trees[method]`. Since `this.trees` is a normal object, HTTP/2 method values like constructor, `toString`, or `__proto__` can resolve inherited object properties instead of returning undefined. The code then treats that value like a router node and crashes when it reaches `currentNode.prefix.length`. ### Patches Upgrade to v9.7.0. ### Workarounds Do not use find-my-way with HTTP/2 servers, or validate that the http method is valid beforehand.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-47219US | — | — | ||
find-my-way is a framework-independent HTTP router that internally uses a Radix Tree and supports route parameters and wildcards. Versions prior to 9.7.0 are vulnerable to remotely… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/delvedor/find-my-wayPACKAGE
- https://github.com/delvedor/find-my-way/commit/cfe3fd6168b5ac1594c0820fb83fce251a533fc1WEB
- https://github.com/delvedor/find-my-way/pull/434WEB
- https://github.com/delvedor/find-my-way/releases/tag/v9.7.0WEB
- https://github.com/delvedor/find-my-way/security/advisories/GHSA-c96f-x56v-gq3hWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan