find-my-way: DDoS with HTTP2

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-47219: 0.46% estimated exploitation activity in the next 30 days; percentile 39.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

23 Jul 2026, 19:33 UTC

Last modified by the source

23 Jul 2026, 19:56 UTC

Source last checked

26 Oct 2026, 12:58 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-c96f-x56v-gq3h

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-c96f-x56v-gq3h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47219

Advisory: find-my-way: DDoS with HTTP2
IDs: CVE-2026-47219, GHSA-c96f-x56v-gq3h
Record: https://patchnext.com/advisories/cve-2026-47219 (revision 2, source checked 26 Oct 2026, 12:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: find-my-way 9.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm find-my-way: affected <= 9.6.0; fixed in 9.7.0

## Suggested inspection (read-only)
- `npm ls find-my-way --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on find-my-way.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-c96f-x56v-gq3h (OSV record GHSA-c96f-x56v-gq3h lists affected ranges: npm find-my-way >=0 <9.7.0 (fixed))
- Verified: https://github.com/advisories/GHSA-c96f-x56v-gq3h (GitHub-reviewed advisory GHSA-c96f-x56v-gq3h lists affected ranges: npm find-my-way >=0 <=9.6.0)

Commands are suggestions: review each one before running it.