CVE-2020-7764 is a high-severity (CVSS 7.5) CWE-444 vulnerability in find-my-way. A fix is available for find-my-way — see the affected versions and patch details below.
Web Cache Poisoning in find-my-way
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
find-my-waynpmDescription
This affects the package find-my-way before 2.2.5, from 3.0.0 and before 3.0.5. It accepts the Accept-Version' header by default, and if versioned routes are not being used, this could lead to a denial of service. Accept-Version can be used as an unkeyed header in a cache poisoning attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | find-my-way | all versions | 2.2.5npm install find-my-way@2.2.5 |
| 📦npm | find-my-way | ≥ 3.0.0&&< 3.0.5 | 3.0.5npm install find-my-way@3.0.5 |
Affected Products
find-my-wayfind-my-way_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for find-my-way, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update find-my-way to 2.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7764 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2020-7764 in your dependencies?
Find it across npm, including transitive dependencies.