CVE-2026-32630: file-type detects the file type of a file, stream, or data

Q: How do I fix CVE-2026-32630?

file-type: upgrade to 21.3.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-32630 being exploited?

CVE-2026-32630 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-32630 affect?

CVE-2026-32630 affects file-type. Severity is medium (CVSS 5.3). 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 fileTypeFro

Q: How urgent is CVE-2026-32630?

Priority 35/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-32630 is a medium-severity flaw (CVSS 5.3) affecting file-type. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-409
Published	2026-03-16
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: sindresorhus

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-16 14:19 UTCPublished CVE record published
2026-06-17 10:36 UTCUpdated Record last modified

sindresorhus file-type UPGRADE

Affected: >= 20.0.0 and < 21.3.2

Fixed in: 21.3.2

Safe to downgrade to: a release before 20.0.0

1. Check installed version

npm ls file-type

2. UPGRADE to 21.3.2

npm install file-type@">=21.3.2"

3. If no update is available yet, DOWNGRADE to a release before 20.0.0

npm view file-type versions npm install file-type@"<20.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-32630?

file-type: upgrade to 21.3.2. Exact commands for each OS are on this page.

Is CVE-2026-32630 being exploited?

CVE-2026-32630 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-32630 affect?

CVE-2026-32630 affects file-type. Severity is medium (CVSS 5.3). 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 fileTypeFro

How urgent is CVE-2026-32630?

Priority 35/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-31808 MEDIUM 5.3 UPGRADE file-type detects the file type of a file, stream, or data

References

← Back to latest CVEs