Process crash via fgetl null terminator overflow
Published Aug 22, 2026 · Updated Aug 22, 2026
Off-by-one heap write in hashcat 7.1.2 and earlier allows attackers to crash the process via a crafted local input file. The fgetl() function in src/filehandling.c accepts line_sz bytes as content and then writes a null terminator at line_buf[line_sz], one byte beyond the allocated heap buffer. Exploitation requires a hash file, potfile, or wordlist with an exact 16,777,216-byte line; a crash is confirmed, while further heap exploitation requires grooming.
Summary
What happened
Off-by-one heap write in hashcat 7.1.2 and earlier allows attackers to crash the process via a crafted local input file. The fgetl() function in src/filehandling.c accepts line_sz bytes as content and then writes a null terminator at line_buf[line_sz], one byte beyond the allocated heap buffer. Exploitation requires a hash file, potfile, or wordlist with an exact 16,777,216-byte line; a crash is confirmed, while further heap exploitation requires grooming.
The record
- CVE
- CVE-2026-68767
- Published
- Aug 22, 2026
- Updated
- Aug 22, 2026
- Vendor
- hashcat
- Product
- hashcat
- Classifications
- CWE-193
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 22, 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 <=7.1.2
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
- Exact-length input file 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