# CVE-2026-32630: file-type affected by ZIP Decompression Bomb DoS via [Content_Types].xml entry

> Attackers can cause denial of service via excessive memory consumption when the library processes crafted ZIP files using buffer or blob detection methods.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-j47w-4g3g-c36v, MINI-5fgc-hh74-w3j7, MINI-8ffp-6hfp-hp4x, MINI-cx7f-gw4m-8fr7, MINI-jp73-mxc3-vfmf, ROOT-APP-NPM-CVE-2026-32630

## What is CVE-2026-32630?

CVE-2026-32630 is a medium-severity denial of service vulnerability in sindresorhus file-type, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

file-type detects the file type of a file, stream, or data. From 20.0.0 to 21.3.1, a crafted ZIP file can trigger excessive memory growth during type detection in file-type when using fileTypeFromBuffer(), fileTypeFromBlob(), or fileTypeFromFile(). The ZIP inflate output limit is enforced for stream-based detection, but not for known-size inputs. As a result, a small compressed ZIP can cause file-type to inflate and process a much larger payload while probing ZIP-based formats such as OOXML. This vulnerability is fixed in 21.3.2.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-32630?

2 open source packages ship an affected version, including file-type. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `file-type` | npm | From 20.0.0 | 21.3.2 |
| `file-type` | npm | From 20.0.0 | 21.3.2 |

Products: Sindresorhus File-Type.

## How do I fix CVE-2026-32630?

Upgrade file-type to 21.3.2 or later.

## Is CVE-2026-32630 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32630 exists.

## Other vulnerabilities in sindresorhus file-type

- [CVE-2022-36313](https://insights.sbomify.com/CVE-2022-36313/): file-type vulnerable to Infinite Loop via malformed MKV file (medium 5.5)
- [CVE-2026-31808](https://insights.sbomify.com/CVE-2026-31808/): file-type affected by infinite loop in ASF parser on malformed input with zero-size sub-header (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32630 and fix it if it is affected.

What it is: CVE-2026-32630 is a medium-severity denial of service vulnerability in sindresorhus file-type, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32630 exists.

Affected packages and fixed versions:
- file-type (npm): affected from 20.0.0; fixed in 21.3.2
- file-type (npm): affected from 20.0.0; fixed in 21.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32630/ (Markdown: https://insights.sbomify.com/CVE-2026-32630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32630
- OSV: https://osv.dev/vulnerability/CVE-2026-32630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32630/
Summaries are generated and may contain mistakes; the official description above is the record.