VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

file-type: vulnerability history, versions and safety

file-type is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 77 releases, from Jul 2022 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 13 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all file-type vulnerabilities

Vulert verdict on file-type 22.2.0 i

Updated on 23 Oct 2026

Good news: 22.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 74/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 22.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 22.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 22.2.0 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 2 in the last year i
  • Latest disclosure 13 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 890 packages i
  • Stars 4,339 i
  • OpenSSF scorecard 2/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for file-type, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
22.2.0 14 Oct 2026 none MIT — Details →
22.1.1 17 Sep 2026 none MIT — Details →
22.1.0 11 Sep 2026 none MIT — Details →
22.0.2 15 Aug 2026 none MIT — Details →
22.0.1 09 Apr 2026 none MIT — Details →
22.0.0 26 Mar 2026 none MIT — Details →
21.3.4 22 Mar 2026 none MIT — Details →
21.3.3 16 Mar 2026 none MIT — Details →
21.3.2 13 Mar 2026 none MIT — Details →
21.3.1 09 Mar 2026 M1 MIT Yes Details →
21.3.0 04 Jan 2026 M2 MIT Yes Details →
21.2.0 25 Dec 2025 M2 MIT Yes Details →
21.1.1 19 Nov 2025 M2 MIT Yes Details →
21.1.0 10 Nov 2025 M2 MIT Yes Details →
21.0.0 23 May 2025 M2 MIT Yes Details →
20.5.0 26 Apr 2025 M2 MIT Yes Details →
20.4.1 13 Mar 2025 M2 MIT Yes Details →
20.4.0 26 Feb 2025 M2 MIT Yes Details →
20.3.0 25 Feb 2025 M2 MIT Yes Details →
20.2.0 24 Feb 2025 M2 MIT Yes Details →
20.1.0 05 Feb 2025 M2 MIT Yes Details →
20.0.1 31 Jan 2025 M2 MIT Yes Details →
20.0.0 15 Jan 2025 M2 MIT Yes Details →
19.6.0 13 Oct 2024 M1 MIT Yes Details →
19.5.0 07 Sep 2024 M1 MIT Yes Details →
19.4.1 14 Aug 2024 M1 MIT Yes Details →
19.4.0 02 Aug 2024 M1 MIT Yes Details →
19.3.0 22 Jul 2024 M1 MIT Yes Details →
19.2.0 17 Jul 2024 M1 MIT Yes Details →
19.1.1 10 Jul 2024 M1 MIT Yes Details →
19.1.0 08 Jul 2024 M1 MIT Yes Details →
19.0.0 07 Jan 2024 M1 MIT Yes Details →
18.7.0 11 Nov 2023 M1 MIT Yes Details →
18.6.0 01 Nov 2023 M1 MIT Yes Details →
18.5.0 04 Jun 2023 M1 MIT Yes Details →
18.4.0 10 May 2023 M1 MIT Yes Details →
18.3.0 25 Apr 2023 M1 MIT Yes Details →
18.2.1 18 Feb 2023 M1 MIT Yes Details →
18.2.0 15 Jan 2023 M1 MIT Yes Details →
18.1.0 11 Jan 2023 M1 MIT Yes Details →
18.0.0 24 Aug 2022 M1 MIT Yes Details →
17.1.6 02 Aug 2022 M1 MIT Yes Details →
17.1.5 02 Aug 2022 M1 MIT Yes Details →
17.1.4 25 Jul 2022 M1 MIT Yes Details →
17.1.3 21 Jul 2022 M1 MIT Yes Details →
16.5.4 21 Jul 2022 M1 MIT Yes Details →
17.1.2 01 Jun 2022 M1 MIT Yes Details →
17.1.1 28 Dec 2021 M1 MIT Yes Details →
17.1.0 27 Dec 2021 M1 MIT Yes Details →
17.0.2 16 Dec 2021 M1 MIT Yes Details →
17.0.1 14 Dec 2021 M1 MIT Yes Details →
17.0.0 24 Nov 2021 M1 MIT Yes Details →
16.5.3 03 Aug 2021 H1 M1 MIT Yes Details →
16.5.2 20 Jul 2021 H1 M1 MIT Yes Details →
16.5.1 10 Jul 2021 H1 M1 MIT Yes Details →
16.5.0 28 May 2021 H1 M1 MIT Yes Details →
16.4.0 05 May 2021 H1 M1 MIT Yes Details →
16.3.0 06 Mar 2021 H1 M1 MIT Yes Details →
16.2.0 13 Jan 2021 H1 M1 MIT Yes Details →
16.1.0 21 Dec 2020 H1 M1 MIT Yes Details →
16.0.1 02 Nov 2020 H1 M1 MIT Yes Details →
16.0.0 18 Oct 2020 H1 M1 MIT Yes Details →
15.0.1 14 Sep 2020 H1 M1 MIT Yes Details →
15.0.0 26 Aug 2020 H1 M1 MIT Yes Details →
14.7.1 07 Aug 2020 H1 M1 MIT Yes Details →
14.7.0 02 Aug 2020 H1 M1 MIT Yes Details →
14.6.2 14 Jun 2020 H1 M1 MIT Yes Details →
14.6.1 07 Jun 2020 H1 M1 MIT Yes Details →
14.6.0 02 Jun 2020 H1 M1 MIT Yes Details →
14.5.0 21 May 2020 H1 M1 MIT Yes Details →
14.4.0 15 May 2020 H1 M1 MIT Yes Details →
14.3.0 04 May 2020 H1 M1 MIT Yes Details →
14.2.0 23 Apr 2020 H1 M1 MIT Yes Details →
14.1.4 11 Mar 2020 H1 M1 MIT Yes Details →
14.1.3 24 Feb 2020 H1 M1 MIT Yes Details →
14.1.2 12 Feb 2020 H1 M1 MIT Yes Details →
14.1.1 05 Feb 2020 H1 M1 MIT Yes Details →
14.1.0 05 Feb 2020 H1 M1 MIT Yes Details →
14.0.0 02 Feb 2020 H1 M1 MIT Yes Details →
13.1.2 22 Jan 2020 H1 M1 MIT Yes Details →
13.1.1 19 Jan 2020 H1 M1 MIT Yes Details →
13.1.0 15 Jan 2020 H1 M1 MIT Yes Details →
13.0.3 09 Jan 2020 H1 M1 MIT Yes Details →
13.0.2 07 Jan 2020 H1 M1 MIT Yes Details →
13.0.1 07 Jan 2020 H1 M1 MIT Yes Details →
13.0.0 07 Jan 2020 H1 M1 MIT Yes Details →
12.4.2 20 Dec 2019 none MIT — Details →
12.4.1 19 Dec 2019 none MIT — Details →
12.4.0 31 Oct 2019 none MIT — Details →
12.3.1 22 Oct 2019 none MIT — Details →
12.3.0 03 Sep 2019 none MIT — Details →
12.2.0 18 Aug 2019 none MIT — Details →
12.1.0 26 Jul 2019 none MIT — Details →
12.0.1 06 Jul 2019 none MIT — Details →
12.0.0 12 Jun 2019 none MIT — Details →
11.1.0 23 May 2019 none MIT — Details →
11.0.0 04 May 2019 none MIT — Details →
10.11.0 11 Apr 2019 none MIT — Details →
10.10.0 01 Apr 2019 none MIT — Details →
10.9.0 05 Mar 2019 none MIT — Details →
10.8.0 18 Feb 2019 none — — Details →
10.7.1 22 Jan 2019 none — — Details →
10.7.0 18 Dec 2018 none — — Details →
10.6.0 03 Dec 2018 none — — Details →
10.5.0 19 Nov 2018 none — — Details →
10.4.0 02 Nov 2018 none — — Details →
10.3.0 01 Nov 2018 none — — Details →
10.2.0 28 Oct 2018 none — — Details →
10.1.0 22 Oct 2018 none — — Details →
10.0.0 07 Oct 2018 none — — Details →
9.0.0 10 Aug 2018 none — — Details →
8.1.0 08 Jul 2018 none — — Details →
8.0.0 12 May 2018 none — — Details →
7.7.1 30 Apr 2018 none — — Details →
7.7.0 29 Apr 2018 none — — Details →
7.6.0 16 Feb 2018 none — — Details →
7.5.0 21 Jan 2018 none — — Details →
7.4.0 01 Dec 2017 none — — Details →
7.3.0 22 Nov 2017 none — — Details →
7.2.0 17 Oct 2017 none — — Details →

The newest 120 of 173 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for file-type

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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
CVE-2026-32630: file-type Package Suffers from ZIP Decompression Bomb DoS Vulnerability 5.3 medium 21.3.2 13 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About file-type

Is file-type safe to use?

Vulert records 3 vulnerabilities for file-type in npm: 0 critical, 1 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is file-type's Vulert package health score?

Vulert scores file-type 74/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of file-type affected?

No. 22.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does file-type have?

3 vulnerabilities are recorded for file-type in the npm ecosystem: 0 critical, 1 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new file-type vulnerabilities disclosed?

2 vulnerabilities were recorded for file-type in the last 12 months, and the oldest entry in this database dates to 22 Jul 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of file-type are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.