Process crash via malformed NTFS timestamp field
Published Mar 11, 2026 · Updated Mar 11, 2026
Off-by-one parsing in yauzl 3.2.0 allows remote attackers to crash Node.js processes through a malformed ZIP NTFS timestamp field. The getLastModDate() loop permits fewer than four bytes to remain before readUInt16LE() reads the tag and size, causing ERR_OUT_OF_RANGE. Exploitation requires a consuming application to accept the crafted ZIP and invoke getLastModDate(); the resulting unhandled exception terminates that process.
Summary
What happened
Off-by-one parsing in yauzl 3.2.0 allows remote attackers to crash Node.js processes through a malformed ZIP NTFS timestamp field. The getLastModDate() loop permits fewer than four bytes to remain before readUInt16LE() reads the tag and size, causing ERR_OUT_OF_RANGE. Exploitation requires a consuming application to accept the crafted ZIP and invoke getLastModDate(); the resulting unhandled exception terminates that process.
The record
- CVE
- CVE-2026-31988
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- Josh Wolfe
- Product
- yauzl
- Classifications
- CWE-193, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.2.0 <3.2.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Minimal malformed NTFS field proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo