Vulnerability Database · npm · file-type · Version
file-type 13.1.1
13.1.1 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 1 Low 0 Unrated 0
-
Released 19 Jan 2020
Licence MIT
Also known from other sources 2
Newer releases 173
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
file-type 13.1.1 vulnerabilities
2 vulnerabilities cover file-type 13.1.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2022-36313: file-type vulnerable to Infinite Loop via malformed MKV file | 7.5 high | 16.5.4 | 22 Jul 2022 |
| CVE-2026-31808: file-type Package Experiences Denial of Service Due to Infinite Loop in ASF Parser | 5.3 medium | 21.3.1 | 10 Mar 2026 |
Looking for another version, or everything Vulert holds for file-type?
Questions
About file-type 13.1.1
Is file-type 13.1.1 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover file-type 13.1.1: 0 critical, 1 high, 1 medium and 0 low. Each entry above names the fixed version to move to.
Is 13.1.1 the latest release of file-type?
No. 13.1.1 was published 19 Jan 2020, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor file-type for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the file-type version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.