CVE-2026-32630
file-type detects the file type of a file, stream, or data. From …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/sindresorhus/file-type/commit/399b0f156063f5aeb1c124a7fd61028f3ea7c124
- github.com/sindresorhus/file-type/security/advisories/GHSA-j47w-4g3g-c36v
- github.com/sindresorhus/file-type/commit/a155cd71323279de173c54e8c530d300d3854fdd
- github.com/sindresorhus/file-type/releases/tag/v21.3.2
- nvd.nist.gov/vuln/detail/CVE-2026-32630
- github.com/advisories/GHSA-j47w-4g3g-c36v
- nvd.nist.gov/vuln/detail/CVE-2026-32630
- cve.org/CVERecord?id=CVE-2026-32630
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.