Process crash via 32-bit multiplication overflow
Published Jun 30, 2026 · Updated Jun 30, 2026
Integer overflow in FuzzyMatchV2 in fzf before 0.73.1 allows local users to crash the process via a crafted input line and pattern. On 32-bit builds, the guard multiplies the input length by the pattern length as an int, so wraparound bypasses the fallback and alloc16 receives a negative slice bound. Triggering the panic requires an approximately 2,200,000-byte line and a 999-byte pattern, and the Go runtime terminates only the affected fzf process.
Summary
What happened
Integer overflow in FuzzyMatchV2 in fzf before 0.73.1 allows local users to crash the process via a crafted input line and pattern. On 32-bit builds, the guard multiplies the input length by the pattern length as an int, so wraparound bypasses the fallback and alloc16 receives a negative slice bound. Triggering the panic requires an approximately 2,200,000-byte line and a 999-byte pattern, and the Go runtime terminates only the affected fzf process.
The record
- CVE
- CVE-2026-53432
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Junegunn Choi
- Product
- fzf
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 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=0 <0.73.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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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