Quick answers
- Is CVE-2026-68767 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68767 being exploited in the wild.
- How severe is CVE-2026-68767?
- Medium severity, with a CVSS score of 6.1, published 22 August 2026.
- Which products and versions are affected?
- Hashcat <UNKNOWN>.
- Is there a fix for CVE-2026-68767?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-68767 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-68767?
- Check whether you run Hashcat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an out-of-bounds heap write in the fgetl() function in src/filehandling.c. The fgetl() function fails to account for the terminating null byte when filling a buffer of exactly HCBUFSIZ_LARGE bytes, writing the null terminator one byte past the buffer's end. An attacker can trigger this by providing a hash file, potfile, or wordlist containing a line of exactly HCBUFSIZ_LARGE bytes. No special authentication is required—the vulnerability is triggered during normal file input processing. The heap write can corrupt adjacent memory structures, leading to denial of service or potentially code execution depending on heap layout and attacker control.
Affected products
- hashcat hashcat <UNKNOWN>
Timeline
- 2026-08-22: disclosed