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

Exp

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.

Published: 2026-03-16 Last update: 2026-03-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-32630 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-32630

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-32630

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-19 0.04% 0.05% +0.01%
2 2026-03-14 0.04%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-32630

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
3.9 1.4 [email protected]

Weakness enumeration for CVE-2026-32630

GitHub Security Advisory for CVE-2026-32630

GHSA-j47w-4g3g-c36v · Severity: medium · Ecosystem: npm — file-type: ZIP Decompression Bomb DoS via [Content_Types].xml entry

OS Trackers for CVE-2026-32630

vendor priority summary link
redhat medium https://access.redhat.com/security/cve/CVE-2026-32630

Affected software / configurations for CVE-2026-32630

Vendor Product Version Raw CPE
sindresorhus file-type >= 20.0.0, < 21.3.2 cpe:2.3:a:sindresorhus:file-type:*:*:*:*:*:node.js:*:*

References for CVE-2026-32630

cvelogic Threat Intelligence