CVE-2026-47219: find-my-way is Vulnerable to DDoS with HTTP2

Published Jul 23, 2026
·
Updated

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.

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
npm/find-my-way<=9.6.0
9.7.0
IBM Concert Software<=1.0.0-3.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/find-my-way to a version that resolves this vulnerability.

    Fixed in 9.7.0
  2. Upgrade

    Upgrade find-my-way to a version that resolves this vulnerability.

    Fixed in 9.0.7
  3. Upgrade

    Upgrade find-my-way to a version that resolves this vulnerability.

    Fixed in 9.7.0
  4. Compensating control

    Do not use find-my-way with HTTP/2 servers, or validate that the HTTP method is valid beforehand.

Event History

Jul 23, 2026
Advisory Published
via GitHub·07:33 PM
Data Sourced
via GitHub·07:33 PM
DescriptionSeverityWeaknessAffected Software
Jul 28, 2026
CVE Published
via MITRE·10:14 PM
Data Sourced
via MITRE·10:14 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:17 PM
DescriptionSeverityWeakness
Sep 22, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-47219?

The severity of CVE-2026-47219 is rated high with a score of 7.5.

2

What type of vulnerability is CVE-2026-47219?

CVE-2026-47219 is a remotely triggerable Denial of Service (DoS) vulnerability.

3

How can CVE-2026-47219 impact my application?

CVE-2026-47219 can cause a Denial of Service in applications using Node's HTTP/2 server with the find-my-way package.

4

How do I fix CVE-2026-47219?

To fix CVE-2026-47219, update to the latest version of the find-my-way package that addresses this vulnerability.

5

Which software is affected by CVE-2026-47219?

CVE-2026-47219 affects the npm/find-my-way package.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203