CVE-2022-36313
HIGHCVE-2022-36313 is a high-severity (CVSS 7.5) CWE-835 vulnerability in file-type. O3 Security confirms whether CVE-2022-36313 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
file-type vulnerable to Infinite Loop via malformed MKV file
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
file-typenpmDescription
An issue was discovered in the file-type package before 16.5.4 and 17.x before 17.1.3 for Node.js. A malformed MKV file could cause the file type detector to get caught in an infinite loop. This would make the application become unresponsive and could be used to cause a DoS attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | file-type | ≥ 13.0.0&&< 16.5.4 | 16.5.4 |
| 📦npm | file-type | ≥ 17.0.0&&< 17.1.3 | 17.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for file-type. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update file-type to 16.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36313 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-36313 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-36313. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-36313 in your dependencies?
O3 detects CVE-2022-36313 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.