Vulnerability in find-my-way (CVE-2026-47219)
Summary
Vulnerability in find-my-way (CVE-2026-47219). Risk of unauthorized operations or information disclosure. Exploitable via req.method. Mitigation: upgrade to 9.7.0 or later.
Original description
The description as published by the source.
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 triggerable DoS in find-my-way when it is used with Node's HTTP/2 server. The lookup() function 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. This issue has been fixed in version 9.0.7.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47219 has been found in find-my-way.
Attackers can target a specific entry point like req.method over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade find-my-way to 9.7.0 or later.
If unsure, ask your IT team or search "find-my-way CVE-2026-47219" on the vendor's site.
CVE-2026-47219 (find-my-way) — CWE-1321 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: req.method / this.trees / toString / __proto__
Patched: 9.7.0 — apply immediately
Workaround: Do not use find-my-way with HTTP/2 servers, or validate that the http method is valid beforehand.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in find-my-way. Attackers reach the vulnerable code path via req.method without authentication.
Check the vendor advisory for the affected versions of find-my-way. Attack surface: req.method / this.trees / toString / __proto__.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 9.7.0.
Workaround: Do not use find-my-way with HTTP/2 servers, or validate that the http method is valid beforehand.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'find-my-way' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'find-my-way' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
find-my-wayを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Do not use find-my-way with HTTP/2 servers, or validate that the http method is valid beforehand.パッチが適用されるまでの応急処置として、Do not use find-my-way with HTTP/2 servers, or validate that the http method is valid beforehand. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade find-my-way to 9.7.0ステージング環境で 9.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com