CVE-2020-8136 — fastify-multipart
HIGHCVE-2020-8136 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in fastify-multipart. 1 public exploit reference exists, so weaponization risk is real. A fix is available for fastify-multipart — see the affected versions and patch details below.
Uncontrolled Resource Consumption in fastify-multipart
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-8136 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
fastify-multipartnpmDescription
Prototype pollution vulnerability in fastify-multipart < 1.0.5 allows an attacker to crash fastify applications parsing multipart requests by sending a specially crafted request.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | fastify-multipart | all versions | 1.0.5npm install fastify-multipart@1.0.5 |
Affected Products
fastify-multipartfastifyResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fastify-multipart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fastify-multipart to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-8136 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-8136 in your dependencies?
Find it across npm, including transitive dependencies.