find-my-way: DDoS with HTTP2
Published Jul 28, 2026 · Updated Oct 24, 2026 · Also known as GHSA-c96f-x56v-gq3h
Original summary
Normalized public record · Updated Oct 24, 2026
find-my-way: DDoS with HTTP2
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Remotely triggerable DoS in find-my-way when it is used with Node's HTTP/2 server.
Potential 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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- 10%
- Aliases
- GHSA-c96f-x56v-gq3h
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Jul 28, 2026 · Last refreshed Oct 24, 2026